Dell PowerStore 5200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 19
B is the Primary Node., a PowerStore Node.
View all Dell PowerStore 5200T manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 19 highlights
Issue ID MDT-365987 MDT-358868 Functional Area Description Support Support Putting a node into service mode or taking a node out of service mode using "svc_rescue_state" service script may fail due to the internal communication issue within a PowerStore Node. Hardware information may be organized in unexpected folders in Data Collections if Node B is the Primary Node. MDT-356926 Support MDT-345925 Support A limit of 500 commands is enforced by the command service that can run before they start queuing up. They will start to queue in the database and not finish execution on time. System Health Check enhancement to improve efficiency MDT-297533 Support Unexpected reboot of a node because of a failure in an internal service MDT-269865 Support MDT-261824 Support MDT-355708 Support Assist MDT-408652 SupportAssist The "svc_node" service script may report an incorrect Chassis Power Status for the peer node as ON when it is actually OFF. If the root file system on a node runs out of space, and the node reboots, the ssh_credentials service can fail. The result is that the SSH keys in use on ESXi can be cleared out affecting communications between the PowerStore X VM and ESXi. Network reconfiguration cannot be performed while SupportAssist without Remote Access is enabled. An internal partition may fill up when SupportAssist is enabled but left disconnected MDT-365450 SupportAssist MDT-303276 SupportAssist MDT-133989 SupportAssist MDT-359883 Virtualization Unable to enable SupportAssist in Gateway mode with a timeout configuration error on some user networks Network firewalls that drop outgoing packets can cause SupportAssist enablement efforts to timeout. It is not possible to reconfigure the system IP addresses while SupportAssist is enabled in 'Gateway Connect without remote access' mode. A node reboot may result in local disk discovery failure due to communication loss between the VM and ESXi host. Resolved Issues 19