Use cases and best practices for HPStorageWorks P2000 G3 MSA FC/iSCSICombo ControllerTechnical white paperTable of contentsAbout this document . 2Intended audience. 2About the HP P2000 Combo Controller. 2Features . 2Benefits. 3Supported operating systems . 3Specifications . 4Use cases . 6Single office with remote site for backup and disaster recovery using iSCSI to replicate data . 6Single office with local site disaster recovery and backup using iSCSI . 7Single office with local site disaster recovery and backup using FC. 8Two branch offices with disaster recovery and backup . 9Single office with target model using FC and iSCSI ports . 10Best practices . 10Using iSCSI and FC at same time. 10Using with Remote Snap . 11For more information. 12

About this documentThis whitepaper introduces features and specifications of the HP StorageWorks P2000 G3 MSAFC/iSCSI Combo Controller. A series of use cases present best practices in setting up and using theHP P2000 Combo Controller.Intended audienceThis paper is intended for entry-level and mid-range HP StorageWorks MSA P2000fc G3administrators and requires previous SAN knowledge.About the HP P2000 Combo ControllerThe HP P2000 Combo Controller is an affordable and flexible solution for small, medium, andenterprise-level IT departments. With both 8 Gb Fibre Channel (FC) and 1GbE iSCSI ports, the HPP2000 G3 is cost effective and ideally positions your department for future growth and expansion.The two 8 Gb Fibre Channel ports enable high speed access to data. The two 1 GbE iSCSI ports allowsmaller departments with tight budgetary restrictions to enjoy shared storage benefits withoutpurchasing their own array, and eliminating the cost of implementing an FC infrastructure.It is also an ideal solution for large companies with multiple smaller departments and/or remotelocations, and smaller companies whose storage needs demand shared resources.The dual-protocol combo capability allows you high speed data access through the 8 Gb FC ports,while designating the two 1 GbE iSCSI ports for Remote Snap.Note:You can use FC for Remote Snap and host I/O simultaneously. While thesystem does not prevent using iSCSI for Remote Snap and host I/Osimultaneously, it is not recommendedFeaturesThe HP P2000 Combo Controller offers the following features: Increased support to seven P2000 LFF disk enclosures (96 LFF drives) Increased support to five D2700 SFF disk enclosures (149 SFF drives) Two new 8 Gb controllers with 2 GB cache memory each:– Standard model with two 8 Gb FC host ports each– Combo model with two 8 Gb FC host ports and two 1 GbE iSCSI ports each 6 Gb SAS back end and HDD support The array supports 512 volumesNote:A snapshot is a special or specific type of volume. Snap pools are anothervolume type2

512 Max LUN support Higher performance with upgraded processing power 64 Snapshots and volume copy capability come standard on G3 models Optional controller-based replication (Remote Snap) Increased I/O performance Improved System Management Utility (SMU) user interface Full support for G1/G2 to G3 upgrade, including cross-protocol upgradesBenefits8 Gb Fibre Channel Suitable for larger or mid-size departments Capable of meeting heavy traffic demands Provides higher performance1 GbE iSCSI Remote Snap Suitable for smaller departments Allow access from outside the FC SAN.Supported operating systemsThe HP P2000 Combo Controller supports a variety of operating systems. For complete details, go toHP’s Single Point of Connectivity Knowledge (SPOCK) website at the following URL: operating system (OS) restrictions apply.3

SpecificationsNumber of Drives149 SFF drives or 96 LFF drives maximum including expansionDrive TypeP2000 300 GB 6G 15K LFF DP ENT SASP2000 450 GB 6G 15K LFF DP ENT SASP2000 600 GB 6G 15K LFF DP ENT SASP2000 1 TB 6G 7.2k LFF DP MDL SASP2000 2 TB 6G 7.2k LFF DP MDL SASMSA2 1 TB 7.2k LFF SATAP2000 2 TB 3G 7.2K LFF MDL SATA72 GB 6G 15K SFF DP SAS146 GB 6G 10K SFF DP SAS300 GB 6G 10K SFF DP SAS146 GB 6G 15K SFF DP SAS500 GB 6G 7.2K SFF DP MDL SASLFF or SFF supported, depending on modelCapacity192 TB Maximum including expansion, depending on modelStorage ExpansionOptionsP2000 3.5-inch disk enclosure or D2700 2.5-inch disk enclosureHost Interface8 Gb Fibre Channel (2) Ports per controller or8 Gb Fibre Channel (2) Ports per controller and1 GbE iSCSI (2) Ports per controllerSupported, depending on modelStorage Controller(2) P2000 G3 Fibre Channel MSA Controller(2) P2000 G3 Fibre Channel/iSCSI Combo MSA ControllerMaximum supported, depending on model. Unable to mix controllers within thearray.4SAN Backup SupportYesOV Storage MirroringSupportYesSystems InsightManager SupportYes

Supported OperatingSystemsMicrosoft Windows Server 2008 IA32, x64, IA64(Standard, Enterprise,Datacenter)Microsoft Windows 2003 R2Microsoft Windows 2003 X64, IA64Red Hat Linux (32/64)SUSE Linux (32/64)HP-UXVMware 3.5, 4.0Citrix XenCombo Controller iSCSI ports support Windows, VMware, Red Hat Linux andSuSE LinuxClustering SupportYesWindows, Linux, HP-UXForm Factor2U5

Use casesThis section of the paper discusses the following use cases demonstrating the capability of the ComboController to operate in both Fibre Channel (FC) and iSCSI mode. See the Remote Snap whitepaperfor more details.For all use cases that provide backup and disaster recovery capabilities, use Remote Snap to replicatedata from one array to the other. The steps to achieve this generally are:1. Install the Remote Snap license. Either use a permanent license that you have bought, or thetemporary license available on the array’s Storage Management Utility (SMU) web-basedinterface.2. Provision storage. Create vdisks, volumes, and snap-pools on both systems.3. Set up the relationship between the systems. Add each system to the other system’s list of remotesystems.4. Create the replication set, specifying the source, or external-view volume, the destination volumeor vdisk, and the protocol (FC or iSCSI) used for replication.5. In case of disaster, you can switch applications over to the backup array.You may want to convert the volumes of the backup array to external-view volumes until theprimary array is back online. Once the primary array is back online, replicate the changes madewhile it was down back to it, and then make its volumes the external-view volumes.Single office with remote site for backup and disaster recovery usingiSCSI to replicate dataFigure 1: Single office with remote site for backup and disaster recovery (iSCSI)This use case illustrates the Combo Controller’s ability to serve data via the FC protocol, and providefor an offsite backup and disaster recovery via the iSCSI protocol, using an existing WAN.6

Single office with local site disaster recovery and backup using iSCSIFigure 2: Single office with local site disaster recovery and backup using iSCSIThis use case is similar to the one above, but exists on one site, rather than using a remote site, anduses your LAN, rather than a WAN, for replication using Remote Snap.7

Single office with local site disaster recovery and backup using FCFigure 3: Single office with local site disaster recovery and backup using FCThis use case is similar to the previous one, but uses FC for replication.8

Two branch offices with disaster recovery and backupFigure 4: Two branch offices with disaster recovery and backupThis use case is similar to the first one, but illustrates that the Combo Controller can be used in anactive-active role, with each system both serving data and acting as backup to the other.9

Single office with target model using FC and iSCSI portsFigure 5: Single office with target model using FC and iSCSI portsThis use case does not use Remote Snap to replicate data to a backup array, but does show theflexibility of the Combo Controller to serve data through both the FC protocol for existing SANservers, and through the iSCSI protocol for those clients and servers that are not currently part of theFC SAN.Note:Accessing a volume both through iSCSI and FC is not supported.Best practicesUsing iSCSI and FC at same time It is not supported for a volume to be mapped via iSCSI and FC at the same time. However theinterface does not prevent this configuration. Use a dedicated LAN for iSCSI traffic. Limit the traffic on the LAN to iSCSI only. However, for thepurposes of replication over a WAN, you’ll probably need to share the link with otherapplications and purposes. Connect the FC and iSCSI ports to a switch – direct connect is not supported for replications,anyway, and connecting to a switch provides more flexibility in your SAN. Connect the two ports of the same type on a controller to different switches. For example A1 andB1 connect to one switch, and A2 and B2 to another. That way, you’re protected against switchfailure as well as controller failure. Plug in both the controllers the system and run it in dual controller mode. Remote Snap is notsupported on single controller arrays.10

Configure all four iSCSI ports with valid IP address and make sure they are connected to theEthernet switch. Make sure all four FC ports are connected to the FC switch. Make sure that both controllers have the same firmware version. Make sure that both local and remote systems are up with same firmware version. You can use the FC port for Remote Snap and host I/O at the same time. You can use FC and iSCSI ports for running I/O (to different LUNs) at the same time.Using with Remote Snap When replicating, put both the volume and snap-pool on the same vdisk, but try to keep any othervolumes off that vdisk. That way, you can detach the volume while disturbing the least number ofvolumes and other components in the array. All replications with which an array is involved must employ one protocol. This means that allreplications must either be iSCSI or FC. You cannot have some replications using iSCSI and someusing FC. Mixed protocol replications are not supported, but the user interface does not preventyou from configuring it that way. If you intend to use Remote Snap, add each array to the other as a Remote System. This is requiredif using the Storage Management Utility (SMU) to configure replication sets, and is also helpful ifusing the Command Line Interface (CLI) to configure replication sets. You must install the Remote Snap license on both the local and remote system11

For more informationFor more information, go to: a list of QuickSpecs, go 3551 div/13551 div.htmlFor all P2000 related manuals and user guides, go t/DocumentIndex.jsp?contentType SupportManual&lang en&cc us&docIndexId 64179&taskId 101&prodTypeId 12169&prodSeriesId 4118559For the HP StorageWorks P2000 G3 MSA System FC/iSCSI User Guide, go t/SupportManual/c02006876/c02006876.pdfFor the HP StorageWorks P2000 Array System Remote Snap Software Technical white paper, go 977ENW.pdfShare with colleagues Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject tochange without notice. The only warranties for HP products and services are set forth in the express warrantystatements accompanying such products and services. Nothing herein should be construed as constituting anadditional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation4AA1-0941ENW, Created July 2010