Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerStore Importing External Storage to PowerStore Guide

PowerStore cluster fibre channel connectivity to source systems

PowerStore operating system version 3.0 or later provides an option to import data from an external source system to a PowerStore cluster using Fibre Channel (FC) connectivity. Except for the Universal type of remote source systems, the World Wide Name (WWN) of the source system is automatically discovered for an FC data connection. The Connection is automatically established from PowerStore to the source system. Host groups are automatically created on the source system with FC initiators and mapped during import.

For the Universal type of remote destination system, the WWN of the destination system is not discovered automatically. In this case, PowerStore Manager lists discovered FC target WWNs during remote system addition. You must select WWNs from the list which belong to the remote system that is being added and proceed with the remote system addition. PowerStore establishes an FC data connection with these selected FC WWNs. After remote system addition, you must create a host on the source system with the FC initiators of all the PowerStore appliances in the PowerStore cluster. The FC initiators of PowerStore are specified as the Import Capable FC ports in each appliance.

Intelligent volume placement occurs within the PowerStore cluster during Import. The host groups are created upon addition of the remote system in PowerStore.

Both agentless and nondisruptive import variants support FC connectivity. However, PowerStore with FC connectivity to a source system supports only FC connectivity with the hosts.

NOTE:The Simple Support Matrix document for PowerStore lists what protocol is supported for the connection between hosts, source system, and PowerStore.

Except for the Universal type of remote source systems, PowerStore creates connection to the remote destinations based on an internal high availability (HA) policy. The system determines the number of connections from an FC initiator to destinations. Each initiator port sequentially connects to a unique destination in each controller, SP, or Director of the respective remote system. Configuration on Node A is applied as is in Node B on a best-effort basis. PowerStore automatically determines the internal HA policy compliance during Create, or Verify, or Connection health change.

For the Universal type of remote source system, you must configure connectivity between the source system and PowerStore as shown in Figure 1. You must select the target FC WWNs in accordance with Figure 1 during remote system addition to ensure that the established connection is compliant with the internal HA policy of PowerStore.

Import capable I/O Module0 Ports

Importing data from an external source system into PowerStore with FC connectivity requires that ports 0 and 1 of PowerStore I/O Module0 are enabled as Dual (as both initiator and target). A maximum of two destinations can be connected from each node, for example:

  • For Dell Unity or Dell VNX2, make connections from each PowerStore node to two different Dell Unity or Dell VNX2 SPs or controllers. For example, connect port P0 of PowerStore Node A and Node B through a switch to the destination port T0 of SPA of the Dell Unity source system. Connect port P1 of PowerStore Node A and Node B through a switch to the destination port T2 of SPB of the Dell Unity source system.
  • For Dell PowerMax or VMAX3, make connections from each PowerStore node to two different Dell PowerMax or VMAX3 directors. For example, connect port P0 of PowerStore Node A and Node B through a switch to the destination port T0 of PowerMax source system Director-X. Connect port P1 of PowerStore Node A and Node B through a switch to the destination port T2 of PowerMax source system Director-Y.
  • For Dell Compellent SC, connection from each PowerStore node is made to two controllers through two fault domains. In case multiple fault domains are configured, make connection to a maximum of two fault domains. For legacy mode, make the connection to primary ports through two different fault domains. Make connections from each PowerStore node to two different Dell Compellent SC controllers. For example, connect port P0 of PowerStore Node A and Node B through Fault Domain 1 to the destination port T0 of Dell Compellent SC source system Controller A. Connect port P1 of PowerStore Node A and Node B through Fault Domain 2 to the destination port T2 of Dell Compellent SC source system Controller B.
See Figure 1 as an example.
Figure 1. FC connections between Controllers of remote system and PowerStore Nodes
FC connections between Controllers of remote system and PowerStore Nodes
Table 1. PowerStore to remote system port configurationThe first column in the table lists the PowerStore Nodes, and the second column lists the port configuration for the FC connections between controllers of the remote system and PowerStore.
PowerStore Node PowerStore (P) to target remote system (T) port configuration
A P0 to T0
P1 to T2
B P0 to T0
P1 to T2
PowerStore ports P0 and P1 on Nodes A and B refer to Fibre Channel I/O Module0 FEPort0 and FEPort1, respectively. The SCSI Mode setting for these ports should be set to Dual (both initiator and target).
NOTE:To view the list of import capable ports on a PowerStore appliance in PowerStore Manager, select an appliance under Hardware, and then select Fibre Channel on the Ports card.

Log in to the source system is initiated after the remote system is added. PowerStore connects only to the allowed list of destinations.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\