Dell PowerStore 3000X EMC PowerStore Release Notes for PowerStore OS Version 1 - Page 3
PowerStore deployment models and configurations, Resolved Issues
View all Dell PowerStore 3000X manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 3 highlights
PowerStore deployment models and configurations Deployment Model Model numbers Support Configurations PowerStore T 1000T Storage-centric deployments. 3000T 5000T 7000T Both block (storage area networks (SAN)) and file (network attached storage (NAS)) services are supported with PowerStore T deployments. Note: Hypervisor deployments are not supported on this model. 9000T PowerStore X 1000X Application and storage-centric deployments. 3000X 5000X Block (SAN-only) storage services with a hypervisor layer installed on the system. The system software is deployed on the hypervisor, which enables deployment of virtual machines (VMs) and customer applications within the hardware. 7000X 9000X Note: File (network attached storage (NAS)) services are not supported on this model. Refer to the PowerStore product support pages (http://www.dell.com/support) for detailed user documentation. Resolved Issues The following high severity issues have been resolved in this release. Issue ID MDT-148696 Functional Area Connectivity - Hosts MDT-153885 Internal Migration MDT-153333 Data Collection Description When there is an active I/O operation occurring between a host and 4-port 32Gb Fibre Channel I/O module on the appliance, and there is a considerable amount of logout and login activity initiated by the hosts, the port may report a BUSY status back to the host even when the port is not oversubscribed from a limits standpoint. If you expand a volume while one of the nodes is booting up, the size of that volume might not change on the node that is booting up. As a result, I/O operations to the newly expanded region of the volume fail if they are sent to that node. As the number of targets scale, node CPU stats may include underlying target stats multiple times inflating the value and causing a discrepancy between appliance CPU stats and its underlying node CPU stats. Resolved Issues 3