HP MPX200 Multifunction Router - Manual (Page 31)

5. Configure IP addresses for the router’s iSCSI ports by entering an IP address:
•
In mpx Manager, modify the iSCSI Port Information page.
•
In the CLI, issue the set iscsi command (see “set iscsi” (page 110) .
To configure the local router and chassis:
1.
Take these preliminary steps:
a.
Ensure that the local router and chassis have access to the source array.
b. Ensure that the LUNs are visible.
c. Create a data management LUN , see “Creating and removing a DML” (page 69) .
d. Configure any potential migration jobs using the destination array (local).
e. If the destination array was initially present at the local site and then moved to a remote
site after the initial copy, ensure that the migration jobs are in a COPY COMPLETE state.
2. Assign IP addresses to the routers iSCSI ports by issuing the set iscsi command , see “set
iscsi” (page 110) .
3. Ensure IP connectivity between the routers by checking for the following:
•
The local router’s MGMT. port can ping the remote router’s MGMT. port.
•
The local router’s network ports can ping the remote router’s iSCSI ports.
4. On each local router blade and chassis, issue the remotepeer add command, for details
see
“remotepeer” (page 101) , and then specify the management port of the remote router. This
step ensures that the remote router has access to the destination array ports and can
communicate using the specified Ethernet ports.
HP recommends the following connections:
•
Blade 1 of the local chassis establishes as the peer Blade 1 of the remote chassis.
•
Blade 2 of the local chassis establishes as the peer Blade 2 of the remote chassis.
5. Validate the configuration by executing the show remotepeers command, see “show
remotepeers” (page 132) .
6. On each blade, issue the array import command, see “array” (page 77) , and then specify
the array to be imported. The imported array is automatically marked as a destination array.
7. Ensure that the array has been imported successfully by issuing the show array command,
see
“show array” (page 112) , and then validating the LUN information.
Each blade should see all of the paths that are available on the peer. However, only the paths
that are online on the peer are online locally.
Adding a Migration Job and resuming an existing Migration Job
You can add a remote migration job using an imported array. You can also enable and disable
compression for the migration job.
If a remote migration job was previously running and the array comes online with the LUNs involved
in the migration, the migration job automatically resumes operation.
For an example of using Native IP to add a remote peer, see “remotepeer” (page 101) .
To remove an imported array, see “Removing an offline array” (page 69) .
Native IP remote migration firewall ports
With Native IP remote migration it may be necessary to open specific ports if a firewall is used in
the network.
Table 6 (page 32) describes the ports that are needed to communicate with the MPX
from the mpx management GUI as well as native IP communications between the local and remote
MPX.
Online remote migration 31