Dell PowerStore 1200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 33

Limitations, PowerStore T and PowerStore X model limitations

Page 33 highlights

Issue ID MDT-111956 MDT-109970 Functional Area Description Virtualization Virtualization In rare cases, the automated mounting of a user-created PowerStore vVol storage container on an ESXi host could fail with the following error message displayed in vCenter "Timed-out waiting to get datastore information from host". Unable to create a vVol storage container in PowerStore, after having just deleted a vVol datastore with the same name from vSphere. Workaround/Resolution Manually mount the vVol storage container from the VMware vSphere GUI or CLI. Either create the vVol storage container in PowerStore using a different name or allow some more time before creating the new vVol storage container in PowerStore with the same name that was used in vSphere. Limitations The following limitations exist in this release. For a complete list of PowerStore limitations see the: PowerStore Simple Support Matrix located on the PowerStore documentation page at: https://www.dell.com/powerstoredocs PowerStore T and PowerStore X model limitations The following limitations exist in PowerStore T and PowerStore X deployment models. Functional Area Importing external storage to PowerStore Internal migration Monitoring PowerStore Clusters PowerStore Management access PowerStore scalability limits SupportAssist Description A maximum of 16 import sessions is supported in the Ready-For-Cutover state during an import. In some cases, when several dozen import operations are run back-to-back, intermittent failures of alternate import sessions may occur. If this occurs, do the following: Remove the remote system and then add it again. Run fewer set of imports (16 or less) at a time. It is recommended to start all these import sessions with automatic cutover turned off. Once all imports have reached the Ready-For-Cutover state, do a manual cutover. After one set of imports is completed, run the next set of imports after a delay of 10 minutes. This delay allows enough time for the system to cleanup any connections to the source system. Prior to performing an internal migration, please refer to Supported Host OS for Non-Disruptive migration of Storage resources at: https://www.dell.com/support/article/en-us/how17129/ for a list of supported configurations and limitations. Starting a new volume mapping job, while another volume mapping job is still in progress, may cause mapping failure due to duplicate Logical Unit Numbers. PowerStore X and PowerStore T appliances are not supported in the same cluster. Use the PowerStore cluster management IP address to access PowerStore Manager and the PowerStore REST API. The appliance management IPs are intended primarily for service use. The PowerStore Simple Support Matrix lists the scalability limitations in PowerStore models. The PowerStore Simple Support Matrix is available from PowerStore documentation page at: https://www.dell.com/powerstoredocs SupportAssist cannot be enabled on PowerStore models configured with IPv6 for the management network. SupportAssist is not supported over IPv6. Limitations 33

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35

Limitations
33
Issue ID
Functional Area
Description
Workaround/Resolution
MDT-111956
Virtualization
In rare cases, the automated mounting of a
user-created PowerStore vVol storage
container on an ESXi host could fail with the
following error message displayed in
vCenter "Timed-out waiting to get datastore
information from host".
Manually mount the vVol storage
container from the VMware vSphere GUI
or CLI.
MDT-109970
Virtualization
Unable to create a vVol storage container in
PowerStore, after having just deleted a vVol
datastore with the same name from
vSphere.
Either create the vVol storage container in
PowerStore using a different name or
allow some more time before creating the
new vVol storage container in PowerStore
with the same name that was used in
vSphere.
Limitations
The following limitations exist in this release. For a complete list of PowerStore limitations see the: PowerStore Simple
Support Matrix located on the PowerStore documentation page at:
PowerStore T and PowerStore X model limitations
The following limitations exist in PowerStore T and PowerStore X deployment models.
Functional Area
Description
Importing external storage to
PowerStore
A maximum of 16 import sessions is supported in the Ready-For-Cutover state during an import.
In some cases, when several dozen import operations are run back-to-back, intermittent failures
of alternate import sessions may occur. If this occurs, do the following:
Remove the remote system and then add it again.
Run fewer set of imports (16 or less) at a time. It is recommended to start all these import
sessions with automatic cutover turned off.
Once all imports have reached the Ready-For-Cutover state, do a manual cutover.
After one set of imports is completed, run the next set of imports after a delay of 10 minutes.
This delay allows enough time for the system to cleanup any connections to the source system.
Internal migration
Prior to performing an internal migration, please refer to
Supported Host OS for Non-Disruptive
migration of Storage resources
at:
for a
list of supported configurations and limitations.
Monitoring
Starting a new volume mapping job, while another volume mapping job is still in progress, may
cause mapping failure due to duplicate Logical Unit Numbers.
PowerStore Clusters
PowerStore X and PowerStore T appliances are not supported in the same cluster.
PowerStore Management
access
Use the PowerStore cluster management IP address to access PowerStore Manager and the
PowerStore REST API. The appliance management IPs are intended primarily for service use.
PowerStore scalability limits
The
PowerStore Simple Support Matrix
lists the scalability limitations in PowerStore models. The
PowerStore Simple Support Matrix is available from PowerStore documentation page at:
SupportAssist
SupportAssist cannot be enabled on PowerStore models configured with IPv6 for the
management network. SupportAssist is not supported over IPv6.