Optionally, add the File Import Interface in
PowerStore Manager
The File Import interface (network) is added when you add the Remote system to
PowerStore Manager.
Every active import requires its own File Import interface be created. However, a File Import interface can be reused for more File Imports when no other session is using it.
NAS Services must be enabled on your
PowerStore T model cluster.
The File Mobility network must be configured in
PowerStore Manager.
The LACP bond that is used for File Import must have been configured on the switch and in
PowerStore Manager.
You can create a Link Aggregation in
PowerStore T model or reuse the Link Aggregation that was configured for NAS services for the File Import interface.
The following network resources must be reserved before you can define the File Import interface in
PowerStore Manager.
The network that is used for File Import is configured while creating the File Import Interface in
PowerStore Manager. You need the following information to set up the File Import network in
PowerStore Manager. For additional requirements to set up a File Import interface and detailed steps see the
PowerStore Importing External Storage to PowerStore Guide.
Table 1. Network configuration worksheet for File Import (completed sample)Lists the resources that are reserved in the sample configuration for the File Import interface.
Resource
File Import
(Optional) VLAN ID
N/A
Netmask/Prefix Length
24
Gateway
192.168.6.1
Network IP addresses
A minimum of one IP address is required for each active file import session. However, a File Import interface can be reused for File Import when no other session is using it.
192.168.6.11
(Optional) Global Storage Discovery IP
It is recommended that you choose to create this IP address. It is used as the single highly available floating IP address for hosts to discover storage from your cluster.
N/A
Map Storage for Appliance/Network Interface Include the Node ports, or port channel on which the networks are configured.
Reuse
BaseEnclosure-NodeA-Bond1 configured for NAS services
If you have not created a Link Aggregation in
PowerStore Manager for the LACP bond you created on the switch for File Import perform the following steps, otherwise continue to step 2.
From
PowerStore Manager, go to the
Hardware page and select the appliance for which you configured the bond.
Open the
Ports card.
Select the two ports on Node A which were configured for the bond on Node A.
You can create a new Link Aggregation or reuse the Link Aggregation that was configured for NAS services for the File Import interface.
Bond 0 is reserved for the Cluster network. You cannot reuse the Link Aggregation that is created for the Cluster network for the File Import interface.
Click
Link Aggregation > Aggregate Links.
PowerStore Manager automatically creates a name for the bond using the following format: "BaseEnclosure-<Node>-<nextLACPbondcreated>" where:
BaseEnclosure is constant.
Node is the node that is displayed in the
Node-Module-Name list.
nextLACPbondcreated the order in which the bond was created in
PowerStore Manager, starting with 0 for the first created bond.
For example, the second LACP bond that is created in
PowerStore Manager on Node A would be named:
BaseEnclosure-NodeA-Bond1.
Optionally, provide a
Description of the bond.
It is recommended to put the name of the bond that is created on the switch that maps to this bond.
The same LACP bond is configured on the opposite node. For example if you configured the LACP bond on Node A, then the same LACP bond would be configured on Node B.
Add the Remote system from the
PowerStore ManagerMigration > Import External Storage > Add Remote System page.
You define the File Import interface while adding the Remote system. See the
PowerStore Manager online help, or the
PowerStore Importing External Storage to PowerStore Guide for details.
Data is not available for the Topic
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: <>()\