Dell PowerStore 1200T EMC PowerStore Networking Guide for PowerStore T Models - Page 97

Create File Mobility in PowerStore Manager

Page 97 highlights

Identifier 6 7 8 9 10 11 Description Node B connection to Bottom, Top-of-Rack Switch 1. Node B connection to Top, Top-of-Rack Switch 1. LACP bond between Node B and the ToR switches. Bottom, Top-of-Rack Switch 1 connection to the remote system. Top, Top-of-Rack Switch 2 connection to the remote system Connection to the remote system. To configure a network for File Import, see Part 2 Add Storage Services. Create File Mobility in PowerStore Manager File Mobility runs over the Management network. File Mobility does not need to be configured on the switch, but must be configured in PowerStore Manager. PowerStore T model must have been deployed in Unified mode. You must reserve 3 IP addressesfor File Mobility. Table 44. IP address assignments for Storage networks IP Address per Assigned to Number of IP Addresses required Appliance Node A 1 Node B 1 Cluster Cluster 1 1. From PowerStore Manager, go to the Settings > Networking > File Mobility tab and click Create. 2. Enter the resources reserved for the File Mobility network into the Create File Mobility Network page and click Create. 3. Map the File Mobility network to the first Management port on Node A (BaseEnclosure-NodeA-EmbeddedModule- MgmtPort). The File Mobility network will automatically be mapped to Node B. NOTE: Reconfiguring the File Mobility interface can be disruptive. Before you reconfigure the File Mobility interface: ● Verify with your network administrator that the configuration information is accurate Ensure that there are no active file migrations or file replication sessions File Mobility 97

  • 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
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118

Identifier
Description
6
Node B connection to Bottom, Top-of-Rack Switch 1.
7
Node B connection to Top, Top-of-Rack Switch 1.
8
LACP bond between Node B and the ToR switches.
9
Bottom, Top-of-Rack Switch 1 connection to the remote system.
10
Top, Top-of-Rack Switch 2 connection to the remote system
11
Connection to the remote system.
To configure a network for File Import, see
Part 2 Add Storage Services
.
Create File Mobility in PowerStore Manager
File Mobility runs over the Management network. File Mobility does not need to be configured on the switch, but must be
configured in PowerStore Manager.
PowerStore T model must have been deployed in
Unified
mode.
You must reserve 3 IP addressesfor File Mobility.
Table 44. IP address assignments for Storage networks
IP Address per
Assigned to
Number of IP Addresses required
Appliance
Node A
1
Node B
1
Cluster
Cluster
1
1.
From PowerStore Manager, go to the
Settings
>
Networking
>
File Mobility
tab and click
Create
.
2.
Enter the resources reserved for the File Mobility network into the
Create File Mobility Network
page and click
Create
.
3.
Map the File Mobility network to the first Management port on Node A (
BaseEnclosure-NodeA-EmbeddedModule-
MgmtPort
).
The File Mobility network will automatically be mapped to Node B.
NOTE:
Reconfiguring the File Mobility interface can be disruptive. Before you reconfigure the File Mobility interface:
Verify with your network administrator that the configuration information is accurate
Ensure that there are no active file migrations or file replication sessions
File Mobility
97