Cx3 40c Iscsi Fc Plan Worksheets

8/22/2019 Cx3 40c Iscsi Fc Plan Worksheets

1/36

Configuration Planning Worksheetsfor CX3-40c Storage Systems

August 8, 2007

This document provides worksheets for you to use in planning theinstallation and configuration of the storage system. These worksheetsassume that you are familiar with the servers (hosts) that will use thestorage systems and with the operating systems on these servers. For eachstorage system that you will configure, complete a copy of the enclosedworksheets.

For the most current, detailed, and complete CX3-series configuration

rules and sample configurations, refer to the E-Lab Interoperability

Navigator on the Powerlink site (http://Powerlink.EMC.com).

The configuration planning guide for the storage systems provides more

information on planning your storage-system configuration, and also includes

copies of these worksheets. You can create a customized version of this documentfrom the user customized documentation link on the Powerlink CLARiiON tools

page or by viewing the version for your storage system on the documentation and

resources CD that shipped with your storage system.

The worksheets in this document are:

Hardware planning worksheets...... ...... ..... ...... ...... ..... ...... ...... ...... .. 2

Storage allocation planning worksheets .......................................... 14 Data replication and mobility planning worksheets .. ... ... ... ... ... ... ... .. 24

1
http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/


2/36

Hardware planning worksheetsThis section contains the following worksheets:

Hardware Components Worksheet, page 2

iSCSI Target and Initiator Port Network Information Worksheet, page 4

iSNS Server Worksheet (Windows environment only), page 6

iSCSI CHAP Authentication Worksheets, page 7

Storage-System Management Ports Worksheet, page 10

CLARalert Worksheet, page 12

Hardware Components Worksheet

Use the Hardware Components Worksheet in Table 1 and the cableplanning template in Figure 1 to plan the hardware components youwant. Some installation types do not have switches or multiple servers.

Table 1 Hardware Components Worksheet

Server information

Server name: Server operating system:

Adapters in server:Server name: Server operating system:

Adapters in server:


Adapters in server:


Adapters in server:

Storage-system components

SPEs: DAEs: Cabinets:

Fibre Channel switch information

32-port: 24-port: 16-port: 8-port:

2 Configuration Planning Worksheets for CX3-40c Storage Systems


3/36

Cables between server and Fibre Channel switch ports cable A

Cable A1 (optical) number: Length (m or ft):




Cables between Fibre Channel switch ports and storage-system SP Fibre Channel data ports cable B

Cable B1 (up to 2 per SPE3 SP, optical) number: Length (m or ft):

Cable B2 (up to 2 per SPE3 SP, optical) number: Length (m or ft):

Cables between network routers or switches and storage-system SP iSCSI data ports cable B

Cable B1 (up to 4 per SPE3 SP, Ethernet) number: Length (m or ft):

Cable B2 (up to 4 per SPE3 SP, Ethernet) number: Length (m or ft):

Cables between enclosures cable C

Cable C1 (copper) number (2 per DAE): Length (m or ft): 1.0 m

Cable C2 (copper) number (2 per DAE): Length (m or ft): 1.0 m

Configuration Planning Worksheets for CX3-40c Storage Systems 3


4/36

EMC3443

Switch 1 Switch 2

Adapter

Adapter

Adapter

Adapter

Adapter

Adapter

B1

B2

Cable betweenserver and switch

Cable betweenswitch and

storage system

Cablebetweenenclosures

LCC LCC

DAE

LCC LCC

DAE

LCC LCC

DAE

LCC LCC

DAE

LCC LCC

DAE

LCC LCC

DAE

SP BSP A

SPEC1

C1

C1

C1

C2 C2

C1

C1

C1

C1

C1

C1

Path 1Path 2

Path 3 not cabled

Path 4 not cabled

A1 AnAmA4

A2A3

Figure 1 Cable planning template for a shared storage system with two back-end

buses (2 front-end cables per SP shown)

iSCSI Target and Initiator Port Network Information WorksheetEach SP has four iSCSI ports, 0 through 3 (labeled 0 iSCSI through3 iSCSI) for connecting the server NICs or iSCSI HBA ports to thestorage system either directly or through a network. These SP iSCSIdata ports are the iSCSI targets and the ports on the server NICs oriSCSI HBAs are the iSCSI initiators.



5/36

Record network information for the iSCSI target ports and iSCSI

initiator ports in Table 2. Descriptions of the fields follow the worksheet.Your network administrator should provide most of this information.

Table 2 iSCSI Target and Initiator Port Network Information Worksheet

iSCSI target port network information

SP A, 0 iSCSI port IP address: Subnet mask: Gateway:




SP B, 0 iSCSI port IP address: Subnet mask: Gateway:




iSCSI initiator port network information

Server name and

port identifier Port IP address Subnet mask Gateway



6/36

iSCSI target port network information

IP addressThe static network IP (Internet Protocol) address (for example,128.222.78.10) for communication with the iSCSI port on the SP. Donot use IP addresses 128.221.1.248 through 128.221.1.255, 192.168.1.1,or 192.168.1.2. These ports should be on different subnets from themanagement ports.

Subnet mask

The subnet mask for the LAN to which the iSCSI port on the SP isconnected.

GatewayGateway address if the LAN to which the iSCSI port on the SP isconnected has a gateway.

iSCSI initiator port network information

Server name and port identifierThe name of the server with the NIC or iSCSI HBA port and anidentifier for that port.

IP addressThe static network IP (Internet Protocol) address (for example,128.222.78.10) for communication with the NIC or iSCSI HBA port.This IP address cannot be 128.221.1.250, 128.221.1.251, 192.168.1.1, or192.168.1.2.

Subnet maskThe subnet mask for the LAN to which the NIC or iSCSI HBA port isconnected.

GatewayGateway address if the LAN to which the NIC or iSCSI HBA port isconnected has a gateway.

iSNS Server Worksheet (Windows environment only)

Enter the public IP address and name of your networks primary iSNSserver and secondary (backup) iSNS server, if you have one, in Table 3.

Note that the public IP address is not related to the servers iSCSI port

addresses.



7/36

Table 3 iSNS Server Worksheet

iSNS server IP address Server name

Primary iSNS server:

Secondary iSNS server:

iSCSI CHAP Authentication Worksheets

If the storage system is on a private LAN, you can elect not to configureCHAP authentication. If the storage system is on a public LAN, westrongly recommend that you set CHAP security. If you do not setCHAP security for the storage system, any host connected to the LANcan read from and write to the storage system.

!CAUTION

Whenever you record any security information such as the CHAPusernames and secrets (passwords), it is imperative that you store thedata in a secure location.

Storage-system CHAP levels

To set up an initiatorCHAP level, you can add one or more usernames

and corresponding secrets. Any initiator configured with one of theseusernames/secrets can establish a connection.

HP-UX and Solaris use the term unidirectional CHAP for initiator CHAP.

To set up a mutual (target) CHAP level, you can create initiator CHAP

so that all initiators can use each username/secret or you can alsouse the iSCSI node name (IQN) to create usernames/secrets that arerestricted for use by a single initiator.

AIX and ESX Server 3.X do not support mutual CHAP. HP-UX and Solaris use

the term bidirectional CHAP for mutual CHAP.



8/36

Initiator CHAP Worksheet

If you want the storage system to authenticate initiators, fill out Table4 for all initiator accounts. Initiator CHAP must be set up and enabledfor iSCSI security to work. The easiest way to configure initiator CHAPis to create a username and secret for all initiators.

Table 4 Initiator CHAP Worksheet

Initiator name:

Use initiator name as system CHAP username (yes or no):

Allow any initiator to log in with this username and secret (yes or no):

CHAP username:

CHAP secret: Specified in hex (yes or no):

Initiator name:



CHAP username:


Initiator name:



CHAP username:


Initiator name:



CHAP username:


Initiator nameThe initiator name is a predefined name that usually begins with iqn(for iSCSI Qualified Name). You can determine the name by running

the SANsurfer utility (shipped with QLogic HBAs) or the Microsoft



9/36

iSCSI Software Initiator for Ethernet NICs. The Microsoft iSCSI

Software Initiator is available on the Microsoft website.Use initiator name as system CHAP usernameIf you want to use the initiator name as the CHAP username, select theUse Initiator Name as System CHAP Username checkbox. If you wantto create a new username, leave the checkbox blank.

CHAP usernameThe CHAP username is a name that you assign for one user or for all

users that connect to the storage system iSCSI port. Either you can usethe same name as the initiator name or you can create a new name. Ifyou use the same name as the initiator name, you are guaranteed tohave a unique name. If you create a new username, that name mightnot be unique unless you are on a private network and create a uniquename for the network.

CHAP secret (password)

For ASCII, the valid range is 12 to 16 printable characters. Forhexadecimal (hex), the valid range is 24 to 32 hexadecimal characters,displayed in pairs. If you want to specify in hex, mark the checkbox.

Allow any initiator to log in with this username and secretTo allow any initiator to log in to the storage system, select the Allowany Initiator to Login with this Username and Secret checkbox. If allinitiators are trusted (for example, in a department or organization),

you might want to select this for convenience. You can always grant orrestrict initiator access to this storage system through the virtual disks.

Mutual CHAP Worksheet

Mutual CHAP management provides an optional extra level of securitythat lets initiators verify the identity of the target storage system. If youwant the initiators to authenticate targets, fill out the Mutual CHAPWorksheet in Table 5 for all mutual CHAP accounts.

Table 5 Mutual CHAP Worksheet

Target CHAP username:

Target CHAP secret (password): Specified in hex (yes or no):



10/36

!CAUTION

Whenever you record any security information such as the CHAPusernames and secrets (passwords), it is imperative that you store thedata in a secure location.

Storage-System Management Ports WorksheetRecord network information for the storage-system management portsin Table 6. Your network administrator should provide most of thisinformation, except for the login information.

Table 6 Storage-System Management Ports Worksheet

Storage-system information

Storage-system serial number:

Network information

IP address SP A: SP B:

Subnet

mask SP A: SP B:

Gateway SP A: SP B:

Login information

Username: Password:Role: Monitor Manager Administrator

Security Administrator


Storage-system serial numberThe hardware serial number (TLA S/N) is on a blue vertical label thatis located on the far left of the chassis behind the front bezel (Figure 2).

To remove the front bezel, unlock it, and then press the latches on its front

sides and pull the bezel toward you.



11/36

EMC3420

Serial number

TLAS

/Nxxxxxxxx

Figure 2 Location of storage-system serial number (front bezel removed)

Network information

IP addressThe static network IP (Internet Protocol) address (for example,128.222.78.10) for communication with a 10/100 management port of astorage processor (SP A or SP B). Do not use IP addresses 128.221.1.248through 128.221.1.255, 192.168.1.1, or 192.168.1.2. Each SP has onemanagement port that must connect to the same subnet as the host usedto initialize the storage system.

Subnet maskThe subnet mask for the LAN to which the storage system is connectedfor management, for example, 255.255.255.0.

GatewayGateway address if the LAN to which the storage-system managementport is connected has a gateway.

Login informationUsernameA username for the management interface. It must start with aletter and may contain 1 to 32 letters and numbers. The name maynot contain punctuation, spaces, or special characters. You can useuppercase and lowercase characters. Usernames are case-sensitive.For example, ABrown is a different username from abrown. Yournetwork administrator may provide the username. If not, then youneed to create one.

PasswordA password to connect to the management interface. It may contain1 to 32 characters, consisting of uppercase and lowercase lettersand numbers. As with the username, passwords are case-sensitive.For example, Azure23 is a different password than azure23. Thepassword is valid only for the username you specified. Your network



12/36

administrator may provide the password. If not, then you need tocreate one.

User rolesFour basic user roles are available - monitor, manager, administrator,and security administrator. All users, except a security administrator,can monitor the status of a storage system. Users with the manager rolecan also configure a storage system. Administrators can maintain useraccounts, as well as configure a storage system. Security administratorscan only manage security and domain settings.

CLARalert Worksheet

Record the network information for the CLARalert monitor stationand the portal system in Table 7.

Table 7 CLARalert Worksheet

Monitor station network information

Host identifier: IP address:

Portal system network information

Portal identifier: IP address: Username: Password:

Monitor station network information

Host identifierThe optional name or description that identifies the Windows hostthat will be the monitor station.

IP addressThe network IP (Internet Protocol) address (for example, 128.222.78.10)for communication with the monitor station. This address must be astatic or DHCP reserved IP address. The portal system uses this IP

address to manage the monitor station.

Since multiple NICs can exist on this station, you must specify an IP address.

This IP address cannot be 128.221.1.250, 128.221.1.251, 192.168.1.1, or 192.168.1.2.



13/36

Portal system network information

Portal identifierOptional identifier (such as a hostname) for the storage system that isor will be the portal system.

IP addressThe network IP address for communicating with the portal system.This IP address is the IP address that you assign to one of the storagesystems SPs when you initialize it.

UsernameThe username for logging into the portal.

PasswordThe password for the username for logging into the portal.



14/36

Storage allocation planning worksheetsThis section contains the following worksheets:

Application and LUN Worksheet, page 14

LUN Details Worksheet, page 15

LUN and Storage Group Worksheet, page 22

Application and LUN Worksheet

Use the Application and LUN Worksheet in Table 8 to list theapplications you will run, and the RAID type and size of the LUN tohold them. For each application that will run, write the applicationname, file system (if any), RAID type, LUN ID (ascending integers,starting with 0), disk space required, and finally the name of the servers

and operating systems that will use the LUN.

Table 8 Application and LUN Worksheet

Application File system, partition,

or drive

LUN RAIDtype LUN ID

(hex)

Disk space

required

(GB)

Server hostname and

operating system

ApplicationEnter the application name or type.



15/36

File system, partition, or driveWrite the planned file system, partition, or drive name here.

With a Windows operating system, the drive letter identifies the LUN.The letter does not help you identify the disk configuration (such asRAID 5). We suggest that later, when you use the operating system tocreate a partition on a LUN, you use the disk administrator softwareto assign a volume label that describes the RAID type. For example,for drive T, assign the volume ID RAID5_T. The volume label willthen identify the drive letter.

LUN RAID typeThis is the RAID group type you want for this file system, partition, ordrive. You can create one or more LUNs on the RAID group.

LUN IDThe LUN ID is a hexadecimal number assigned when you bind thedisks into a LUN. By default, the ID of the first LUN bound is 0, the

second 1, and so on. Each LUN ID must be unique within the storagesystem, regardless of its storage group or RAID group.

The maximum number of LUNs supported on one host bus adapterdepends on the operating system.

Disk space required (GB)Consider the largest amount of disk space this application will need,and then add a factor for growth.

If sometime in the future, you find that you need more space for this

application, you can expand the capacity of the LUN by adding other LUNs to

it. For information on expanding LUNs, refer to the Navisphere Manager online

help, which is available on the Powerlink website (http://Powerlink.EMC.com).

Server hostname and operating system

Enter the server hostname (or, if you do not know the name, a shortdescription that identifies the server) and the operating system name,if you know it.

LUN Details Worksheet

Use the LUN Details Worksheet in Table 9 to plan the individual LUNs.Complete as many blank worksheets as needed for all LUNs in storage

systems. For unshared storage, skip the storage group entries.

http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/


16/36

Table 9 LUN Details Worksheet


Storage-system number or name:

Storage-system installation type: Unshared direct Shared-or-clustered direct Shared switched

SP A information

IP address or hostname: Port ALPA ID: Memory (MB):

SP B information

IP address or hostname: Port ALPA ID: Memory (MB):

Cache information

Read cache size: Write cache size: Cache page size:

LUN information

LUN ID:SP owner: SP A SP B

SP back-end bus (0 or 1):

RAID group ID: RAID group size (GB): LUN size (GB): Disk IDs:

RAID type:RAID 6 RAID 5 RAID 3 RAID 1 mirrored pair RAID 0 RAID 1/0 Individual disk

Hot spare

Read and write Write only Read only NoneCaching:


Servers that can access this LUNs storage group:

Operating system information

Device name: File system, partition, or drive:



17/36

LUN information

LUN ID: SP owner: SP A SP B SP back-end bus (0 or 1):



Hot spare





Device name: File system, partition, or drive:

LUN information

LUN ID:SP owner: SP A SP B

SP bus (0 or 1)



Hot spare





Storage-system name or number

Enter the number or name that identifies the storage system.Storage-system installation typeSpecify unshared direct, shared-or-clustered direct, or shared switched.

MemoryEnter the amount of memory on the SP.



18/36

SP A and SP B information

IP addressEnter the IP address or hostname for the SP. The IP address is requiredfor communication with the SP. You do not need to complete it now,

but you will need it when the storage system is installed so that youcan set up communication with the SP.

Port ALPA IDFor shared storage (switches), the SP ALPA ID is ignored for all except

HP-UX servers. For unshared storage, each SP connected to a servermust have a unique SP Port ALPA ID; for example, for two storagesystems, use IDs 0, 1, 2, and 3. The SP Port ALPA ID, like the IPaddress, is generally set at installation.

Cache information

You can use SP memory for read/write caching. You can use differentcache settings for different times of day. For example, for user I/O

during the day, use more write cache; for sequential batch jobs at night,use more read cache. Generally, write caching improves performancefar more than read caching. Read caching is nonetheless crucial forgood sequential read performance, as seen in backups and table scans.The ability to specify caching on a LUN basis provides additionalflexibility, since you can use caching for only the units that will benefitfrom it. Read and write caching is recommended for any type ofRAID group, particularly RAID 6 or RAID 5. You enable caching forspecific LUNs allowing you to tailor your cache resources accordingto priority.

The maximum cache size per SP is 3016 MB, and the maximum writecache size is 2500 MB.

Read cache sizeIf you want a read cache, we recommend for a storage system with themaximum cache memory that the read cache should be about 516 MB,which is the amount available per SP after assigning the maximumallowed amount to the write cache.

Write cache sizeGenerally, for a storage system with the maximum cache memory, werecommend that the write cache should be the maximum allowed size,which is 2500 MB per SP.



19/36

Cache page sizeCache page size applies to both read and write caches. It can be 2, 4, 8,or 16 KB. As a general guideline, we suggest 8 KB. The ideal cache pagesize depends on the operating system and application.

LUN information

LUN IDThe LUN ID is a hexadecimal number assigned when you bind thedisks into a LUN. By default, the ID of the first LUN bound is 0, the

second 1, and so on. Each LUN ID must be unique within the storagesystem, regardless of its storage group or RAID group. The maximumnumber of LUNs supported on one host bus adapter depends on theoperating system.

SP ownerThe SP owner is the SP that will own the LUN: SP A or SP B. You canlet the management program automatically select the SP to balance the

workload between SPs; to do so, leave this entry blank.SP back-end buses

Each SP supports two physical back-end buses that are paired with thecounterpart SP to create two redundant buses (buses 0 and 1). If youhave both 2 Gb/s and 4 Gb/s disks, you should put the 2 Gb/s diskson one bus and the 4 Gb/s disks on the other bus. Ideally, you shouldplace the same amount of load on each bus. This may mean placing

two or three heavily used LUNs on one bus and six or seven lightlyused LUNs on the other bus.

The bus designation appears in the disk ID (form b-e-d, where b is theback-end bus number, e is the enclosure number, and d is the diskposition in the enclosure). For example, 0-1-3 indicates the fourth diskon bus 0, in enclosure 1 (numbering 0, 1, 2, 3... from the left) in thestorage system.

RAID group IDThis ID is a hexadecimal number assigned when you create the RAIDgroup. By default, the number of the first RAID group in a storagesystem is 0, the second 1, and so on, up to the number of disk drives inthe system.

RAID group sizeEnter the user-available capacity in gigabytes (GB) of the whole RAID

group. You can determine the capacity as follows:



20/36

RAID group Disk capacity (GB)

RAID 6 group disk-size x (number-of-disks - 2)

RAID 5 or RAID 3 group disk-size x (number-of-disks - 1)

RAID 1/0 or RAID 1 group (disk-size x number-of-disks) / 2

RAID 0 group disk-size x number-of-disks

Individual unit disk-size

Usable disk space differs from the drive size reported by themanufacturer. A drive manufacturers definition of a gigabyte is1,000,000,000 bytes and the storage systems "true" definition is 1024x 1024 x 1024, or 1,073,741,824 bytes. Typical conversions are shown

below.

Available GB

Listed Capacity Disk 0-4 (vault disk) Other

73 GB 33.64 GB 66.61 GB

146 GB 100.68 GB 133.65 GB

300 GB 235.40 268.37

500 GB N/A 458.56

750 GB N/A 687.86

Notes: 500-GB and 750-GB are ATA disks and they cannot be used as vault disks (disk 0-4)

For example:

A 6-disk RAID 6 group or 5-disk RAID 5 or RAID 3 group of 300-GBdisks holds either 941.62 GB if all disks are vault disks (disks 0-4) or1073.48 GB if it does not include vault disks.

A 4-disk RAID 1/0 group of 300-GB disks holds either 470.81 GBif all disks are vault disks or 536.74 GB if it does not include vault

disks.

A RAID 1 mirrored pair of 300-GB disks holds either 235.40 GBif the pair includes vault disks or 268.37 GB if it does not includevault disks.

An individual disk (RAID 1) of a 300-GB disk holds either 235.40GB if it is a vault disk or 268.37 GB if it is not a vault disk.



21/36

LUN sizeEnter the user-available capacity in gigabytes (GB) of the LUN. You canmake this the same size or smaller than the RAID group. You mightmake a LUN smaller than the RAID group size if you want a RAID5 group with a large capacity and you want to place many smallercapacity LUNs on it; for example, to specify a LUN for each user.

Multiple LUNs per disk group share the same total performance capability

of the disk drives, so plan carefully.

If you want multiple LUNs per RAID group, then use a RAIDgroup/LUN series of entries for each LUN.

Disk IDsEnter the IDs of all disks that will make up the LUN or hot spare. Theseare the same disk IDs you specified on the previous worksheet. Forexample, for a RAID 5 group in a DAE on bus 0 (disks 10 through 14),

enter 0010, 0011 , 0012, 0013 , and 0014.

RAID typeCopy the RAID type from the previous worksheet; for example, RAID5 or hot spare. For a hot spare (strictly speaking not a LUN at all), skipthe rest of this LUN entry and continue to the next LUN entry (if any).

CachingIf you want to use caching, you can specify the type of caching youwant read and write, write, read, or none for this LUN.

Servers that can access this LUNs storage groupFor shared switched storage or shared-or-clustered direct storage, enterthe name of each server (copied from the LUN and storage groupworksheet). For unshared direct storage, this entry does not apply.


Device nameEnter the operating system device name, if this is important and if youknow it. Depending on your operating system, you may not be ableto complete this field now.

File system, partition, or driveWrite the name of the file system, partition, or drive letter you willcreate on this LUN. This is the same name you wrote on the application

worksheet.



22/36

On the following line, write any pertinent notes; for example, the filesystem mount-point or graft-point directory pathname (from the rootdirectory). If any of this storage systems LUNs will be shared withanother server, and the other server is the primary owner of this LUN,write secondary. (As mentioned earlier, if the storage system will beused by two servers, we suggest you complete one of these worksheetsfor each server.)

LUN and Storage Group Worksheet

Use the LUN and Storage Group Worksheet in Table 10 to select thedisks that will make up the LUNs and storage groups in each storagesystem. Unshared storage systems do not use storage groups. Forunshared storage, skip the storage group entry.

Table 10 LUN and Storage Group Worksheet


Storage group ID or name: Server hostname:Dedicated

Shared

LUN ID or name: RAID type: Capacity (GB): Disk IDs:






Shared








23/36


Shared





Complete as many of the storage system sections as needed for allthe storage groups in the SAN (or as needed for all the LUNs withunshared storage). Copy the (blank) worksheet as needed.

For shared storage, if a storage group will be dedicated (not accessibleby another server in a cluster), mark the Dedicated box at the end of itsline; if the storage group will be accessible to one or more other serversin a cluster, write the hostnames of all servers and mark the Shared box.

For unshared storage, ignore the Dedicated/Shared boxes.



24/36

Data replication and mobility planning worksheetsThis section contains the following worksheets:

SnapView worksheets, page 24

MirrorView/A worksheets, page 27

MirrorView/S worksheets, page 30

SAN Copy worksheets, page 32

SnapView worksheets

The worksheets in Table 11, Table 12, and Table 13 will help you planyour clones and snapshots. The first worksheet is for clone planning;the second is for snapshot planning; the third is for reserved LUN poolplanning for snapshots.

Clone Worksheet

The Clone Worksheet in Table 11 will help you plan for clones. Notethat the size of the clone private LUNs (one for each SP) is fixed and itis quite modest, so the worksheet does not include it.

Note: With SnapView version 6.24 or later, a clones source LUN can be a

remote mirror LUN (a LUN participating as either a primary or secondary

image).



25/36

Table 11 Clone Worksheet

LUN

Production

hostname Source LUN ID Storage group ID Size (GB)

Application, file system, or database

name



26/36

Snapshot Worksheet

For each SnapView session, you must complete a Snapshot Worksheetin Table 12. Note that you must assign the LUN and snapshotto different storage groups. One storage group must include theproduction host and source LUN; another storage group must includethe second host and the snapshot.

Table 12 Snapshot Worksheet

LUN

Reserved LUN

pool

Production

hostname

Source

LUN ID

Storage

group ID

Size

(MB)

Application,

file system, or

database name

LUN ID or

name

Size

(MB)

SP (both

LUN and

cache)

Time of

day to

copy

Session

name

Reserved LUN Pool Worksheet

Since snapshots use the reserved LUN pool, you need the followinginformation for system setup so you can bind LUNs for the reservedLUN pool. The number of reserved LUNs should always be twice thenumber of source LUNs. Note that MirrorView/A and incrementalSAN Copy also use the reserved LUN pool. One application can use areserved LUN as long as another application is not using it.



27/36

The Reserved LUN Pool Worksheet in Table 13 is also provided in theMirrorView/A and incremental SAN Copy sections.

Table 13 Reserved LUN Pool Worksheet

SP (A or B)

Only for

Navisphere

Manager6.22 or

earlier Source LUN size

RAID type for

reserved LUN pool

RAID group ID of

parent RAID group

Reserved LUN size

(GB)

Reserved LUN IDor name (complete

after binding)

Notes: For Navisphere 6.24 or later you no longer assign LUNs in the reserved LUN pool to an SP, so the first column of the worksheet

SP (A or B) is not needed. We recommend that the reserved LUN size is 20% of the source LUN size.

MirrorView/A worksheets

The worksheets in Table 14 and Table 15 will help you plan your remoteasynchronous mirrors. The first is for mirror planning, and the secondis for reserved LUN pool planning.

You must assign each primary image LUN to a storage group (as withany normal LUN), but you must not assign a secondary image LUN toa storage group. If primary image LUNs are in a consistency group, allsecondary image LUNs must be on the same remote storage system.



28/36

The worksheet in Table 16 will help you plan iSCSI connection setsfor iSCSI replication.

Table 14 Remote Asynchronous Mirrors Worksheet

Production

hostname

Primary

LUN ID,

size, and

file system

name

Storage

group

number

or name

Use write

intent log

(Y/N)

SP

(A/B)

Remote

mirror

name

Secondary

hostname

Secondary

image LUN

ID

Group name (if

applicable)

Since MirrorView/A uses the reserved LUN pool, you need thefollowing information for system setup so you can bind LUNs for thereserved LUN pool. The number of reserved LUNs should always betwice the number of source LUNs. A MirrorView/A primary imageLUN is a source LUN. Note that SnapView and incremental SAN Copy

also use the reserved LUN pool. One application can use a reservedLUN as long as another application is not using it.

The Reserved LUN Pool Worksheet in Table 15 is also provided in theSnapView and incremental SAN Copy sections.



29/36


SP (A or B)Only for

Navisphere

Manager

6.22 or


RAID type for

reserved LUN pool

RAID group ID of

parent RAID group

Reserved LUN size

(GB)

Reserved LUN ID

or name (complete

after binding)



If you are using iSCSI MirrorView/A replication, fill out the informationin Table 16 for the iSCSI connection sets that you want to configure.



30/36

Table 16 iSCSI Connection Sets Worksheet

Connection pathUniqueconnection set

name

Optional

username

Optionalpassword

(secret)

Credential usage(specific, shared,

none)

iSCSI

initiator port

Target system IP

address

Target iSCSI

port

MirrorView/S worksheets

The worksheets in Table 17 and Table 18 help you plan your remotemirrors. The first worksheet is for remote mirror planning, and thesecond is for the optional write intent log planning. You must assigneach primary image LUN to a storage group (as with any normal LUN),

but you must not assign a secondary image LUN to a storage group.




31/36

Table 17 Remote Synchronous Mirrors Worksheet

Production

hostname

PrimaryLUN ID,

size, and

file system

name

Storage

group

number or

name

Use write

intent log

(Y/N)

SP

(A/B)

Remote

mirror name

Secondary

hostname

Secondary

image LUN

ID

Group

name (if

applicable)

Notes: By default, newly created remote mirrors do not use the write intent log, so you do not need to allocate space for the write intent

log. However, before you use it, you must allocate space for it. If you want to use the write intent log, enter Y, and, after completing the

worksheet, fill out the Write Intent Log Worksheet on the next page.

If you decide to use the write intent log feature for even one remotemirror, then you must bind two LUNs of at least 128 MB for the writeintent log.

Table 18 Optional Write Intent Log Worksheet

LUN LUN name or ID LUN size (128 MB minimum)

First LUN

Second LUN



32/36

If you are using iSCSI MirrorView/S replication, fill out the informationin Table 19 for the iSCSI connection sets that you want to configure.


Connection pathUnique

connection set

name

Optional

username

Optional

password

(secret)

Credential usage

(specific, shared,

none)

iSCSI

initiator port

Target system IP

address

Target iSCSI

port

SAN Copy worksheets

The worksheets in Table 20, Table 21, and Table 22 will help you planSAN Copy sessions. The first worksheet is for sessions between storagesystems; the second is for sessions within the same storage system; andthe third is for reserved LUN pool planning.


One of the storage systems in the session must be a SAN Copy storage system,

that is, it must have SAN Copy installed on it.



33/36

Table 20 SAN Copy Worksheet for a Session Between Storage Systems

Session nameSAN Copy storage-system name

Source storage-system name

Source logical unit name

Destination storage-system name

Destination logical unit names

For a SAN Copy session between logical units in the same storagesystem, the same SP must own the logical units.

Table 21 SAN Copy Worksheet for a Session Within a Storage System

Session name

Source storage-system name

Source logical unit name

Destination logical unit names

Incremental SAN Copy uses the reserved LUN pool, so if you wantto use this type of SAN Copy, you need the following informationfor system setup so you can bind LUNs for the reserved LUN pool.The number of reserved LUNs should always be twice the number of

source LUNs. Note that MirrorView/A and SnapView also use thereserved LUN pool. One application can use a reserved LUN as long asanother application is not using it.

The Reserved LUN Pool Worksheet in Table 22 is also in the SnapViewand MirrorView/A sections.



34/36


SP (A or B)Only for

Navisphere

Manager

6.22 or


RAID type for

reserved LUN pool

RAID group ID of

parent RAID group

Reserved LUN size

(GB)

Reserved LUN ID

or name (complete

after binding)



If you are using iSCSI MirrorView/A replication, fill out the informationin Table 23 for the iSCSI connection sets that you want to configure.



35/36


Connection pathUniqueconnection set

name

Optional

username

Optionalpassword

(secret)

Credential usage(specific, shared,

none)

iSCSI

initiator port

Target system IP

address

Target iSCSi

port



36/36

Copyright 20062007 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. Theinformation is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATIONMAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TOTHE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED

WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires anapplicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks onEMC.com.

All other trademarks used herein are the property of their respective owners.


Cx3 40c Iscsi Fc Plan Worksheets

Documents

Transcript of Cx3 40c Iscsi Fc Plan Worksheets