Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

Dell PowerStore Importing External Storage to PowerStore Guide

PDF

Configure the connection to a remote system for file-based import

Prerequisites

Once the file import interface has been configured, you can add the remote system to establish the import connection with which to connect to the PowerStore appliance. You need to enter the IP address of the source SPA or SPB and the credentials of a user with administrator privileges on the source system when you add the remote system. After adding the remote system, you are ready to create your file import session.

Ensure the following:

  • For a source VNX system with two control stations, the home directory of a user with the Administrator role, which is used in configuring the remote system connection, must exist on the primary control station of the VNX.
  • The remote system does not already exist in the list of remote systems.
  • For a VDM import, ensure file import interfaces are configured on each node of the destination system.
  • The relevant SP and node pair (source SPA and destination Node A or source SPB and destination Node B) are up and running.
  • If STIG is enabled for the PowerStore cluster, ensure the SSL certificate of the VNX2 system is FIPS compliant with a SHA256 signature algorithm.
    NOTE:If the VNX2 system SSL certificate uses a non FIPS compliant signature algorithm, make the following changes for IP_ADDR, HOSTNAME_SHORT, HOSTNAME_LONG, x509_extensions, and default_md in the configuration file /nas/http/conf/celerrassl.cnf on the VNX2 system:
    • IP_ADDR = <management IP address of VNX system>
    • HOSTNAME_SHORT = <HOSTNAME_SHORT for VNX>
    • HOSTNAME_LONG = <HOSTNAME_LONG for VNX>
    • x509_extensions = v3_ca
    • default_md = sha256
    After the changes have been made in the configuration file, run the following openssl command for signature algorithm conversion: 
    • usr/bin/openssl req -x509 -nodes -sha256 -days 365 -newkey rsa:2048 -keyout ssl.key/ssl_key.<HOSTNAME for VNX>-CS0 -out ssl.crt/ssl.crt.<HOSTNAME for VNX>-CS0 -config /nas/http/conf/celerrassl.cnf
    After the conversion completes, check the algorithm using the following command: 
    • /usr/bin/openssl x509 -in ssl.crt/ssl.crt.<HOSTNAME for VNX>-CS0.crt -text
NOTE:When adding a Unified VNX2 remote system for importing external storage and the block import capability is added successfully but the file Import capability fails, the add remote system operation should still be successful. However, a File Not Ready alert should appear in Unisphere which means that the add remote system for file has failed. The remote system for file failure can occur for a number of reasons, for example, incorrect service password, or SSH is disabled. Identify and fix the issue, and then do one of the following:
  • Run the Verify and Update operation to retry adding the file replication capability.
  • Run the Modify operation to retry adding the file import capability.

Obtain the SP IP management address and associated user credentials that will be used to connect to the source system.

Steps

  1. In PowerStore Manager, under Migration select Import External Stroage.
  2. Perform one of the following actions:
    • To add a remote system for file import to PowerStore, select +Add. On the Add Remote System slide out panel, specify the relevant information.
    • To modify an import connection, select the remote system and then select Modify. On the Connection Properties window, specify the relevant SP (SPA or SPB) IP address, username, and password to authenticate to the SP of the source storage system.
    • If new file import interfaces were added, or existing file import interfaces were deleted, the source system information may become outdated. Select the relevant remote system, and then select Verify and Update to update the source system information to pick up the latest file import interface changes on the destination and source systems.
    • If new source storage resources were added, or existing source storage resources were deleted or modified after you add a remote system and before you create an import session to the source system, you need to re-discover the source storage system resources. Select the relevant remote system and then select Discover to re-discover the source system resources.
    • To delete a remote system, select the remote system, and then under More Actions select Delete.
      NOTE:Before you delete a remote system, ensure that all ongoing or scheduled block imports are allowed to complete or be cancelled and all file import sessions are deleted before deleting the remote system. Deleting a remote system is idempotent. The remote system is updated to Partial_delete on failures. In these cases, the delete remote system operation can be retried to complete the delete.

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: <>()\