HP MPX200 Data Migration Planning Guide

Table 11 Example: physical device information
LUN ID
Physical disk or raw device
nodeVolume
Mount point (if
any)ApplicationServer
0, 1Disk0, Disk1 (Dynamic Disks)F:\F:\SharepointSharepointHR-Dept
0/dev/sdb/dev/sdb/data/webinfoApache Web
Server
iPortal
0, 1, 2/dev/rdsk/ c0t1d0
/dev/rdsk/ c0t1d1
/dev/rdsk/ c0t1d2
/dev/vg-2/ vol2/home/oracleOracleSales
List and create LUN ID mappings
Table 12 (page 19) shows LUNs presented to the MPX200 at LUN IDs that are different from the
IDs presented to the server. You can use the LUN remapping feature later to present LUNs to the
server with the original LUN IDs. Through the MPX200, a different LUN from a storage array is
presented as the same LUN ID (2) on two different servers: HR-Dept and iPortal.
Table 12 Example: LUN ID mappings
CapacityDestination LUNSource LUNCapacityVolume ID,
source
Source
LUN seen
Server
Presented
to server
as LUN ID
Presented
to
MPX200
as LUN ID
Remapped
and
presented
to host
Presented
to
MPX200
as LUN ID
array (if
applicable)
by the
server as
LUN
through
MPX200
at LUN ID
200GB0000100GB10HRDept.
500GB1111250GB21
250GB0202250GB30iPortal
300GB0303300GB40Sales
300GB1414300GB51
300GB2525300GB62
List and create FC zoning
Table 13 (page 19) assumes a redundant configuration:
• Two FC switches
• Multiple servers, each with two adapter ports
• One storage array with two controllers
• Four ports per controller
Table 13 Example A: pre-migration FC zoning information
Server, MPX200, storage nameZone members (WWPNs)FC Zone name
FC Switch and IP
address
HR-Dept: P121-00-00-C0-DD-C0-8A-D7Zone-AFC-SW-1 10.5.3.1
iPortal: P121-00-00-C0-DD-C0-55-57
Sales: P121-00-00-C0-DD-C0-60-66
SRC-Array-ABC: P150-06-01-60-41-E0-18-94
SRC-Array-ABC: P350-06-01-62-41-E0-18-94
HR-Dept: P221-00-00-C0-DD-C0-8A-D8Zone-BFC-SW-2 10.5.3.2
List and create LUN ID mappings 19