b series remote rep_best practices

HP StorageWorks

B-Series remote replication solution

best practices guide

Part number: 5697-6731First edition: June 2007

Legal and notice information

© Copyright 2007 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensedto the U.S. Government under vendor’s standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forthin the express warranty statements accompanying such products and services. Nothing herein should be construed as constitutingan additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or itssubsidiaries in the United States and other countries.

Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation.

Adobe and Acrobat are trademarks of Adobe Systems Incorporated.

Java is a US trademark of Sun Microsystems, Inc.

Oracle is a registered US trademark of Oracle Corporation, Redwood City, California.

UNIX is a registered trademark of The Open Group.

Printed in the US

Contents

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . 7Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Rack stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8HP websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Hardware and software considerations . . . . . . . . . . . . . . . . 13HP StorageWorks storage arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Required components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

HP software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13HP hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Optional components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Solution components requirements and considerations . . . . . . . . . . . . . . . . . . . . . . 15

HP StorageWorks 400 Multi-Protocol Router/MP Router blade . . . . . . . . . . . . . . . . 15HP B-Series SAN infrastructure (switches/directors) . . . . . . . . . . . . . . . . . . . . . 15HP StorageWorks 4x00/6x00/8x00 EVA family . . . . . . . . . . . . . . . . . . . . . . 15HP StorageWorks Continuous Access software . . . . . . . . . . . . . . . . . . . . . . . 16

3 Solution setup overview . . . . . . . . . . . . . . . . . . . . . . 17Solution configuration concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

B-Series fibre channel-to-fibre channel routing . . . . . . . . . . . . . . . . . . . . . . . 17Meta SANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Backbone fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18LSAN zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Edge fabric view of a Meta SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Meta SAN design considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Fibre channel over Internet Protocol (FCIP) . . . . . . . . . . . . . . . . . . . . . . . . . 20Backbone fabric limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Sample topologies and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22400 MP Router and MP Router blade fabric architecture . . . . . . . . . . . . . . . . . . . 22Continuous Access EVA configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Overall Setup Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4 Solution setup . . . . . . . . . . . . . . . . . . . . . . . . . . 29Configuring FCIP on the HP StorageWorks 400 MP Router/MP Router blade . . . . . . . . . . . . 29Configuring Fibre Channel routing (FCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . 32HP StorageWorks Continuous Access configuration procedure . . . . . . . . . . . . . . . . . . 33

Disk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33DR groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33DR group log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

HP cluster technologies for disaster-tolerant solutions . . . . . . . . . . . . . . . . . . . . . . 34HP Serviceguard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34HP Storageworks Cluster Extension EVA . . . . . . . . . . . . . . . . . . . . . . . . . . 34HP Metrocluster/HP Continentalclusters . . . . . . . . . . . . . . . . . . . . . . . . . . 35

B-Series remote replication solution 3

5 Tools for managing and monitoring the replication network . . . . . . 37HP StorageWorks Continuous Access EVA Performance Estimator . . . . . . . . . . . . . . . . . 37Solution testing with EVA workloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38HP StorageWorks B-Series tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

WAN analysis tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Procedure description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

6 Related information . . . . . . . . . . . . . . . . . . . . . . . 45Dark Fiber/WDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45XP array family and Continuous Access XP . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7 Appendix: . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Configuring FCIP interfaces and tunnels on the HP StorageWorks 400 MP Router using CLI commands . 47HP StorageWorks Fabric Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

HP StorageWorks Fabric Manager share devices wizard . . . . . . . . . . . . . . . . . . . 50Viewing LSANS using Fabric Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4

Figures

1 ..Simplest Meta SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 ..Meta SAN with four edge fabrics . . . . . . . . . . . . . . . . . . . . . . . . . 193 ..Edge fabrics #1 logical view of Meta SAN . . . . . . . . . . . . . . . . . . . . 194 ..Simplest Meta SAN with FCIP . . . . . . . . . . . . . . . . . . . . . . . . . . 205 ..Dedicated backbone fabric Meta SAN . . . . . . . . . . . . . . . . . . . . . . 216 ..Dedicated backbone fabric with common devices . . . . . . . . . . . . . . . . . . 227 ..Continuous Access EVA two-fabric FCIP-router configuration . . . . . . . . . . . . . 238 ..Continuous Access EVA 4–fabric FCIP router configuration . . . . . . . . . . . . . . 249 ..Continuous Access EVA five-fabric FCIP-router configuration . . . . . . . . . . . . . 2510 ..Continuous Access EVA 6–fabric FCIP router configuration . . . . . . . . . . . . . . 2611 ..Continuous Access EVA six-fabric FCIP-router with dedicated backbone fabrics configuration 2712 ..HP StorageWorks Continuous Access EVA Replication Performance Estimator-V3 . . . . . 38


Tables1 ..Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 ..Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 ..Required hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 ..Optional components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 ..Inter-site link parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 ..Backbone fabric vs. edge fabric limitations . . . . . . . . . . . . . . . . . . . . 217 ..FCIP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 ..Port mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6

About this guide

This guide provides information about:

• Deployment of the HP disaster recovery/remote replication B-series solution across the HPStorageWorks Enterprise Virtual Array (EVA) family

• Design considerations specific to the HP StorageWorks B-Series SAN Infrastructure and HPStorageWorks Continuous Access EVA

• Deployment of the HP StorageWorks 400 Multi-Protocol Router and/or Multi-Protocol Routerblade in the HP StorageWorks SAN Director 4/256

• Tools for managing and monitoring the network

Intended audienceThis guide is intended for:

• Technical personnel involved in the deployment of the disaster recovery/remote replication solution• Channel partners and resellers

Related documentationThe following documents and websites provide related information:

• HP StorageWorks Enterprise Virtual Array homepage: http://www.hp.com/go/eva• HP StorageWorks Continuous Access EVA software homepage: http://www.hp.com/go/caeva• HP StorageWorks SAN design reference guide: http://www.hp.com/go/sandesignguide• HP StorageWorks B-Series documentation: http://www.hp.com/go/san• HP StorageWorks B-Series remote replication solution whitepaper: http://www.hp.com/go/

bseriesreplication

Document conventions and symbolsTable 1 Document conventions

Convention Element

Blue text: Table 1 Cross-reference links and e-mail addresses

Blue, underlined text: http://www.hp.com website addresses

Bold text

• Keys that are pressed• Text typed into a GUI element, such as a box• GUI elements that are clicked or selected, such as

menu and list items, buttons, tabs, and check boxes

Italic text Text emphasis

Monospace text• File and directory names• System output• Code


http://www.hp.com/go/eva












http://www.hp.com/go/caeva












http://www.hp.com/go/sandesignguide












http://www.hp.com/go/san












http://www.hp.com/go/bseriesreplication













http://www.hp.com

Convention Element

• Commands, their arguments, and argument values

Monospace, italic text• Code variables• Command variables

Monospace, bold text Emphasized monospace text

WARNING!Indicates that failure to follow directions could result in bodily harm or death.

CAUTION:Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT:Provides clarifying information or specific instructions.

NOTE:Provides additional information.

TIP:Provides helpful hints and shortcuts.

Rack stabilityRack stability protects personnel and equipment.

WARNING!To reduce the risk of personal injury or damage to equipment:• Extend leveling jacks to the floor.• Ensure that the full weight of the rack rests on the leveling jacks.• Install stabilizing feet on the rack.• In multiple-rack installations, fasten racks together securely.• Extend only one rack component at a time. Racks can become unstable if more than one component

is extended.

HP websitesFor additional information, see the following HP websites:

• http://www.hp.com• http://www.hp.com/go/storage• http://www.hp.com/service_locator

8 About this guide

http://www.hp.com

http://www.hp.com

http://www.hp.com

http://www.hp.com

http://www.hp.com

http://www.hp.com

http://www.hp.com/go/storage












http://www.hp.com/service_locator









• http://www.hp.com/support/manuals• http://www.hp.com/support/downloads

Documentation feedbackHP welcomes your feedback.

To make comments and suggestions about product documentation, please send a message [email protected]. All submissions become the property of HP.


http://www.hp.com/support/manuals












http://www.hp.com/support/downloads












10 About this guide

1 Overview

This document describes how to deploy an HP disaster recovery/remote replication B-Series solution. Itfocuses on a replication solution using Continuous Access EVA and FCIP, and the deployment of the HPStorageWorks 400 Multi-Protocol Router and/or Multi-Protocol Router Blade in the HP StorageWorksSAN Director 4/256.

The document includes sections on:• Hardware and software considerations, page 13• Solution setup overview, page 17• Solution setup, page 29• Tools for managing and monitoring the replication network, page 37• Related Information, page 45• Appendix, page 47

For information on the need for disaster recovery and design considerations and factors that influence thedesign and implementation of a disaster recovery/remote replication solution, see the HP StorageWorksB-Series remote replication solution whitepaper: http://www.hp.com/go/bseriesreplication. For detailedinformation on the deployment of Continuous Access EVA, see the HP StorageWorks Continuous AccessEVA planning guide: http://www.hp.com/go/caeva. For more information on SAN design, see theSAN Design reference guide: http://www.hp.com/go/sandesignguide

NOTE:There are similar replication recovery solutions available using the HP XP array family and ContinuousAccess XP, and intersite link technologies other than FCIP.






































12 Overview

2 Hardware and softwareconsiderations

HP StorageWorks storage arraysThe HP StorageWorks Enterprise Virtual Array family (EVA) is designed for customers in thebusiness-critical enterprise marketplace, offering a high performance, high availability virtual arraystorage solution. The EVA is designed for the data center where there is a critical need for improvedstorage utilization and scalability. Remote replication (both synchronous and asynchronous) is supportedfor the HP StorageWorks EVA family, and replication can be performed between the same or differentmodels of the EVA. Enhanced asynchronous replication, which increases the support for long distancereplication, is available for the EVA 4x00/6x00/8x00 family, running XCS v6.x or later firmware.

Required components

HP softwareTable 2 Required software

Required software Software description

HP StorageWorks Continuous Access EVA software(separate license)

HP StorageWorks Continuous Access EVA softwareis an array-based application that provides disastertolerant remote replication for the entire EVA productfamily.

HP StorageWorks Replication Solutions Manager(RSM)

Continuous Access EVA software utilizes the HPStorageWorks Replication Solutions Manager (RSM)interface to create, manage and configure remotereplication on the full HP StorageWorks EnterpriseVirtual Array product family. HP Replication SolutionsManager integrates both local and remote replicationinto a simple to use GUI and CLI. RSM removes almostall of the complexity of configuring and managingreplication environments through easy to use wizardsand automation of common tasks.

HP StorageWorks Command View EVA software HP StorageWorks Command View EVA Software isa comprehensive software suite designed to simplifyarray management of the HP StorageWorks EnterpriseVirtual Array (EVA) family of storage array products.The suite allows the administrator to discover, monitor,and configure the HP StorageWorks EVA diskarrays from a single Web-based console, providingmaximum control over the HP storage environment.

B-Series licenses FCIP SAN Services License (allows FCIP Tunneling)


HP hardwareTable 3 Required hardware

Required hardware Hardware description

HP StorageWorks B-Series SAN infrastruc-ture—switches/directors

The HP StorageWorks 400 Multi-Protocol Router/MPRouter blade is compatible with all HP-supportedB-Series SAN switches/directors, as specified in theHP StorageWorks SAN Design reference guide.

HP StorageWorks 400 Multi-Protocol Router/MPRouter blade

HP StorageWorks 400 Multi-Protocol Router is afixed-configuration 16-port 4-Gb FC switch withtwo additional ports for FCIP connectivity. The HPStorageWorks B-Series Multi-Protocol Router bladeis an option for the HP StorageWorks SAN Director4/256. The blade has 18 ports: 16 Fibre Channeland 2 Gigabit Ethernet. The blade, as an option tothe director, inherits the high availability attributes ofthe director platform. Both provide the following SANservices: FC switching, FC-FC SAN routing (FCR) andFCIP tunneling.

Optional componentsTable 4 Optional components

Optional components Description

HP StorageWorks Cluster Extension EVA software Offers protection against application downtimefrom fault, failure, or site disaster by extending alocal cluster between data centers over metropolitandistances. CLX EVA integrates with open-systemclustering software (Microsoft Cluster Service in theWindows 2003 environments and HP Serviceguardfor Linux in Red Hat and SuSe Linux environments)and HP StorageWorks Continuous Access EVA toautomate failover and failback between sites.

HP Metrocluster / Continentalclusters with ContinuousAccess EVA

Disaster tolerant solutions for HP-UX 11i. Bothsolutions are built upon HP Serviceguard, HP-UX’sfoundation clustering software, and are integratedwith Continuous Access EVA. Both provide automatichands-free failover/failback of application services.

HP StorageWorks Fabric Manager A highly scalable, Java-based application thatmanages multiple B-series switches and fabricsin real-time, providing the essential functionsfor efficiently configuring, monitoring, dynamicprovisioning, and managing SAN fabrics on adaily basis. Fabric Manager includes wizards fordeploying the B-Series Multi-Protocol router.

HP StorageWorks 400 Multi-Protocol Router PowerPack/HP StorageWorks 4/256 SAN Director PowerPack

The Power Pack models of the 400 MP Router and theSAN Director provide additional B-Series softwarelicenses. The MP Router Blade inherits these licensesfrom the Director, if installed. If FCIP functionality isrequired, an additional license (as mentioned abovein the required component list) is required; again, ifthe Director chassis is licensed, the blade will inheritthe license.

14 Hardware and software considerations

Solution components requirements and considerationsThis section highlights information to consider when building the data replication solution.

HP StorageWorks 400 Multi-Protocol Router/MP Router blade• Use the MP Router blade, if there are available slots in the HP StorageWorks 4/256 SAN

Director; otherwise, use the standalone 400 Multi-Protocol Router. See the HP StorageWorks SANDesign reference guide at http://www.hp.com/go/sandesignguide for additional information onthe 400 MP Router and MP Router Blade fabric rules.

• A minimum of two routers (standalone or blade) that communicate with the FCIP protocol mustbe installed at each site for path redundancy over the WAN.

• 400 MP Router/MP Router blade installed for use with Continuous Access EVA must have theexchange-based routing feature disabled. Follow the steps below to disable exchanged-basedrouting default setting:1. Open a telnet session.2. Enter aptpolicy.

Current Policy: 33: Default Policy1: Port Based Routing Policy3: Exchange Based Routing Policy

3. Enter switchdisable.4. Enter aptpolicy 1.

Policy updated successfully.5. Enter switchenable.6. Enter aptpolicy.

Current Policy: 1• The 400 MP Router or MP Router blade must NOT be configured for FastWrite acceleration.• In-order delivery (IOD) of frames during a fabric topology change should be enabled (default).

To verify the setting, enter iodshow. If IOD is not set, enter iodset.• Dynamic Load Sharing (DLS) must be disabled. Use dlsreset to disable DLS. Enter dlsshow

to verify the setting.

HP B-Series SAN infrastructure (switches/directors)• The default routing policy for B-Series switches is set to “Exchange Based Routing Policy”. Change

the routing policy to “Port Based Routing Policy” for all switches on the SAN used by ContinuousAccess EVA for replication traffic. Use the following command: aptpolicy 1. (See theexample under HP StorageWorks 400 Multi-Protocol Router/MP Router blade)

• Dynamic Load Sharing (DLS) must be disabled for all switches on the SAN used by ContinuousAccess EVA for replication traffic. Use dlsreset to disable DLS.

• In-order delivery of frames during a fabric topology change should be enabled (default).

HP StorageWorks 4x00/6x00/8x00 EVA family• For enhanced asynchronous remote replication, both arrays must be runing XCS firmware v6.x. With

the enhanced asynchronous mode, Continuous Access EVA uses a buffer-to-disk implementation thatincreases the support for long distance replication.

• Replication between all EVA family models (EVA3000/4x00/5000/6x00/8x00) is possible, butenhanced asynchronous replication is available only on the EVA4x00/6x00/8x00 family arrays.

• For low bandwidth inter-site links, using separate EVA ports for host I/O and replication I/O ishighly recommended.














HP StorageWorks Continuous Access softwareHP StorageWorks Continuous Access mandates certain inter-site link parameters in order to haveoptimal performance.

Table 5 Inter-site link parameters

Specification Description

IP Bandwidth 1 Must be dedicated to the Continuous Access storagereplication function.

Maximum number of DR Groups

See the tables in the HP StorageWorks SAN designreference guide for minimum supported bandwidthbased on the average packet-loss ratio and one-wayinter-site latencies.

Maximum transmission unit (MTU) of the IP network 1500 bytes / 2250 bytes

Maximum latency 1 100 ms IP network delay one-way or 200 msround-trip

Average packet-loss ratio2Low-loss network: 0.0012% average over 24 hoursHigh-loss network: 0.02% average over 24 hours;must not exceed 0.05% for more than 5 minutes in a2-hour window.

Latency jitter3 Must not exceed 10ms over 24 hours

1Pre-existing condition2A high packet-loss ratio indicates the need to retransmit data across the inter-site link. Each retransmission delaystransmissions queued behind the current packet, thus increasing the time to complete pending transactions and lowering theperformance predictability.3Latency jitter is the difference between the minimum and maximum values, and indicates how stable or predictable thenetwork delay. The greater the jitter, the greater the variance in the delay, which lowers the performance predictability.

See the SAN extensions section in the HP StorageWorks SAN design reference guide:http://www.hp.com/go/sandesignguide for details on inter-site parameters and maximum allowable DRgroups based on different bandwidths and latencies.

16 Hardware and software considerations













3 Solution setup overview

Solution configuration concepts

B-Series fibre channel-to-fibre channel routingFC-to-FC Routing is a technology that logically connects physically separate fabrics (SAN islands) toenable selective shared access to resources from any fabric, with the benefits of administration andfault isolation of separately managed fabrics. FC routing does not merge the fabrics, so the issuesassociated with merging fabrics, such as Domain ID overlaps and Zoning conflicts, do not apply. FCrouting provides selective device connectivity via Logical Storage Area Networks (LSANs), but preventsFibre Channel services (e.g. FC Name Server) from propagating between fabrics. As a result, disruptionsto a fabric are contained, and have less impact than would be the case without FC routing. Anotherbenefit of FC routing is that it allows each fabric to maintain independent administration, thus preventingfabric administrator errors from propagating between fabrics in addition to isolating failures in hardwareor software. For example, if an administrator at one site accidentally deletes the fabric-wide zoningconfiguration, with FC routing in place, this will not propagate to other sites.

Another advantage FC routing provides is that the scalability of one edge fabric does not affectanother; fabric reconfigurations do not propagate between edge fabrics, and faults in fabric servicesare contained. Furthermore, if FC routing is used with legacy switches, the overall network size canvastly exceed the hardware and software capabilities of those switches. None of these features are truewith one large merged fabric.

There are a number of new terms associated with the FC routing that need to be defined in order tounderstand the design concepts of using FC routing between FC SANs.

Meta SANsWhen FC switches are connected directly to each other via Inter-Switch Links (ISLs), they form a fabric. Adual redundant SAN is an unconnected pair of redundantly configured fabrics.

When multiple fabrics are connected through a FC-to-FC router, they form a different kind of SAN. Theresulting FC-routed Storage Area Network is a level above the common definition of SAN and is calleda Meta SAN, or sometimes a routed FC SAN.

At a minimum, a Meta SAN consists of one and only one backbone fabric and one or more edge fabrics,and the backbone fabric must contain at least one MP Router. For high availability, you may configure adual redundant Meta SAN just as you would configure a dual redundant SAN.


Figure 1 Simplest Meta SAN

Backbone fabricThe backbone fabric is the functional element that makes the logical connection between edge fabrics,or between the backbone fabric and an edge fabric. The backbone fabric, at a minimum consists, ofat least one MP Router, but can contain more than one MP Router and standard FC switches in thebackbone fabric. MP routers and FC switches in the backbone fabric are linked via a standard ISLthat is no different from any other FC fabric. The key factor that distinguishes the backbone fabricis its connection to the edge fabrics.

This connection between the backbone fabric and the edge fabric(s) is via an Inter-Fabric Link (IFL). Thebackbone fabric side of the link is configured as an EX_Port while the edge fabric side of the link isconfigured as an E_Port. This EX_Port is a version of the E_Port, and to the edge fabric, it appears like anordinary connection to any other FC switch. The main difference between an E_Port and an EX_Port isthat the EX_Port makes the backbone fabric appear to be a single FC switch to the edge fabric, regardlessof the number of MP Routers and FC switches that are in the backbone fabric.

The EX_Port is always the boundary point between the backbone fabric and an edge fabric and is intheory part of the edge fabric. Figure 1 shows that the edge fabric includes all the FC switches and theIFL up to and including the EX_Port of the backbone fabric.

With the 400 MP Router and the MP Router Blade, a limited number of hosts and/or storage devicesmay be connected to the backbone fabric. These devices can be routed to the edge fabrics. Host andstorage devices connected to the backbone fabric that contains a 2 Gb MP Router are not routable toany edge fabric.

LSAN zoningLSAN zoning is the methodology that allows a subset of devices from separate fabrics to communicate.An LSAN zone looks like any other zone in a fabric, with the exception that the zone name must beginwith LSAN_ (case insensitive). Day-to-day administration of LSAN zones is performed using the zoningtools within each fabric. This allows existing tools to work as usual, and minimizes the need to retrainSAN administrators. If this specially named LSAN zone is created on two or more fabrics to which an MPRouter has access to, the MP Router will automatically create the Logical Storage Area Networks (LSANs)between those fabrics. If an LSAN spans two fabrics, there are two LSAN zones that define it—one oneach fabric. An LSAN that spans three fabrics would have three LSAN zones, and so on.

The name of the LSAN zone in the separate fabrics does not need to be the same, but the WWN of thedevices from ‘local’ and ‘remote’ fabrics must be in an LSAN zone in both fabrics.

TIP:While LSAN zones are not required to use the same name, it is recommended that you use the same orsimilar names to aid in troubleshooting.

LSAN zoning only supports WWN zoning, as Port Identifiers (PID) are not unique in the fabric and, infact, two devices with exactly the same PID in two different fabrics can communicate via an LSAN zone.


NOTE:LSAN zones in the backbone fabric with a 2 Gb MP Router are not supported.

Edge fabric view of a Meta SANTo the edge fabric, the MP Router’s EX_Port looks like any other FC switch in the edge fabric. However,the EX_Port blocks the edge fabric from seeing the real topology of the backbone fabric or any switchesin any other edge fabrics. To the edge fabric, the backbone fabric appears to be one switch, regardlessof the number of switches in the backbone fabric or the number of IFLs between the edge fabric andthe backbone fabric.

In addition to this single logical switch that represents the backbone fabric, the backbone fabric willpresent one other logical switch for each ‘remote’ edge fabric that has devices shared between edgefabrics. Regardless of the number of switches and shared devices in the remote edge fabric, the localedge fabric will only see that entire remote edge fabric as a single logical FC switch.

Figure 2 Meta SAN with four edge fabrics

Using the Meta SAN depicted in Figure 2 as an example, and assuming that LSAN zones are deployed,allows sharing of devices between the three edge fabrics: edge fabric#1, edge fabrics #2, and edgefabric #4. Edge fabric #1‘s logical view of the Meta SAN appears as in Figure 3.

Figure 3 Edge fabrics #1 logical view of Meta SAN

In Figure 3, edge fabric #1 sees the backbone fabric as a single FC switch regardless of the numberof MP Routers, FC Switches, IFLs, or shared devices there are in the backbone fabric. Likewise, each“remote” edge fabric with devices routed to edge fabric #1 logically appears to be a single FC switchconnected to the logical switch that represents the backbone fabric.


NOTE:The edge fabric #3 is not presented to edge fabric #1 because, in the example, no LSAN zones forthat fabric exist.

For this example, if a FabricShow command is executed on any FC switch in edge fabric #1, it listsall physical FC switches in edge fabric #1 and three other logical switches: one logical switch for thebackbone fabric and one for each edge fabric that has devices routed to edge fabric #1. The names ofthe logical switches in the FabricShow output are FCR_FD_# for the backbone fabric and FCR_XD_#for each of the remote edge fabrics, where # represents the domain identifier assigned to the logicalswitch. This also applies to the backbone fabric and any remote edge fabric that have devices routed toedge fabric #1.

Any devices routed to edge fabric #1 appear connected to the logical switch that represents that fabricand has a Port Identifier (PID) based on the domain identifier of that logical switch.

NOTE:Only devices properly configured in LSAN zones will be presented to edge fabric #1.

Meta SAN design considerations• The SAN extension technology to be used to connect the fabrics• Whether an existing fabric or a new dedicated fabric will be used for the backbone fabric

Fibre channel over Internet Protocol (FCIP)Two additional port terms need defining when Fibre Channel over Internet Protocol (FCIP) is usedbetween MP Routers.

• VE_Port−A Virtual E_Port is an IP/Ethernet interface on an MP Router configured as an E_Port. Itis equivalent to a FC E_Port, except the protocol on the link is FCIP.

• VEX_Port−A Virtual EX_Port is an IP/Ethernet interface on an MP Router configured as an EX_Portand is equivalent to a MP Router EX_Port, except the protocol on the link is FCIP.

Figure 4 Simplest Meta SAN with FCIP

The EX_Port or VEX_Port for FCIP is the boundary point between the backbone fabric and an edgefabric and, in theory, is part of the edge fabric. This does not have much impact on selecting thebackbone fabric when using Native Fibre Channel or WDM technologies for the SAN extensionmedium; however, with FCIP this adds another consideration to the design of a Meta SAN.In Figure 4, the edge fabric includes all the FC switches in the edge fabric and the IFL/FCIP link upto the VEX_Port. Because the VEX_Port is part of the edge fabric, the IP network also becomes partof the edge fabric. Since the IP network is probably the most unstable component in the fabric, thefabric(s) that contain the IP network will see more disruptions than a fabric without an IP network.


Backbone fabric limitationsThe backbone fabric is the functional element that makes the logical connection between edge fabrics, orbetween the backbone fabric and an edge fabric. There are some limitations in terms of the number ofFC Routers, FC switches and devices that are supported in the backbone fabric.

Table 6 Backbone fabric vs. edge fabric limitations

FOS Version

FOS 5.1 FOS 5.2

Max # of device ports per backbone fabric 256 512

Max # of device ports per edge fabric 1000 1200

Max # of fibre channel switches per backbone fabric 10 10

Max # of fibre channel switches per edge fabric 26 26

NOTE:The 2 Gb MP Router does not support FC routing on any device in the backbone fabric to any edge fabric.

NOTE:When you install the MP Router blade in the 4/256 SAN Director and create an EX_Port/VEX_Port, thatDirector and the fabric attached to the Director immediately become part of the backbone fabric. That is,all the non-router blades in the chassis become part of the backbone fabric, and the fabric containingthe Director becomes limited in scalability and port connectivity.

With the scaling limitations of the backbone fabric, it might seem intuitive to select the smaller site tobe the backbone fabric, but if FCIP is utilized as the SAN Extension technology, the larger site (edgefabric) will have the IP network as part of its fabric. Since the IP network is the most unstable part of thisconfiguration, the fabric that contains the IP network(s) will see more disruptions than a fabric without theIP network. HP recommends not including the IP network as part of the Primary site, while not limiting thescalability of the site’s fabric(s). To do this, implement the type of configuration referred to as a dedicatedbackbone fabric as described in Sample topologies and configurations, page 22.


Figure 5 Dedicated backbone fabric Meta SAN

Utilizing a Dedicated Backbone as shown in Figure 5 can solve the backbone fabric scaling and FCIP IPnetwork issues. By implementing a dedicated backbone fabric, no existing production fabric has thebackbone fabric scaling limitations imposed on it, and generally the number of FC switches and deviceson this dedicated fabric are smaller and within the current limitations.

In addition to eliminating the scaling restrictions, when FCIP is used as the SAN extension technology, theIP network is now part of the backbone fabric rather then any of the individual edge fabrics. Each sitehas a piece of the backbone fabric and, if the IP network goes down, the edge fabrics will only see aRegistered State Change Notification (RSCN) rather than the fabric transition the edge fabric would see ifthe IP network were a part of that edge fabric.

The MP Router portion of the backbone fabric at each site could also contain common devices sharedbetween multiple edge fabrics at that site. For example, if Site #1 had several edge fabrics and wantedto share a tape library system, the tape subsystem could be placed on the MP Router that is the interfaceto the backbone fabric for the site’s edge fabrics.

Figure 6 Dedicated backbone fabric with common devices

Sample topologies and configurationsThe following includes configurations that use the HP StorageWorks 400 MP Router and/or the MPRouter blade for implementing a FCIP disaster recovery solution. The configuration concepts from theprevious section are discussed in context with these configurations.

400 MP Router and MP Router blade fabric architectureThere are four proven SAN extension solutions that can be implemented with various director/switch/routercombinations, depending on the size of the SAN and the availability level required:

• 2–fabric architecture: used for smaller SANs with lower throughput and connectivity levels• 4–fabric architecture: used for smaller SANs, providing higher availability than the 2–fabric

solution.• 5–fabric architecture: used when larger scalability is required, and for I/O write-intensive

situations


• 6–fabric architecture: provides the highest availability level

By using the B-Series directors and standalone switches capabilities, and the combination of FibreChannel routing, switching, and SAN extension, the physical configuration can be reduced to fewerelements to drive additional simplification and ease of maintenance.

Continuous Access EVA configurationsThe 400 MP Router and MP Router blade support the HP standard Continuous Access EVA replicationconfigurations. This includes the two-fabric, four-fabric, five-fabric, six-fabric and six-fabric with dedicatedbackbone fabric implementations as shown in Figure 7, Figure 8, Figure 9, Figure 10, and Figure 11.These five configuration examples are all drawn showing 400 MP Routers; however, they could all beimplemented using the MP Router blade or a combination of both.

Figure 7 shows a typical 2-port EVA 6000/5000/4000/3000 configuration of a Continuous Accesstwo-fabric LSAN replication zone solution. In this configuration, zoning is used to separate host trafficfrom replication traffic in the fabric. Standard B-Series zoning is used for one port from each EVAcontroller for local host access as in any other fabric. The other EVA port on each controller is dedicatedto replication traffic, and LSAN zoning is used to enable the Fibre Channel Routing feature of the MPRouter to allow these devices to communicate across the FCIP Link as if they were in the same fabric.

This is the lowest cost configuration. However, no path redundancy is provided, and therefore thisconfiguration does not provide any redundancy in the event of a fabric or WAN failure. In addition, theIP network is part of the remote site fabric, and the local site fabric is the backbone fabric.

Figure 7 Continuous Access EVA two-fabric FCIP-router configuration

Figure 8 shows a typical 4-port EVA 8000 configuration of a Continuous Access four-fabric LSANreplication zone solution. Like the previous configuration, zoning is used to separate host traffic fromreplication traffic in each fabric. In each fabric, standard B-Series zoning is used for two ports from eachEVA controller for local host access as in any other fabric. The other EVA ports on each controllerare dedicated to replication traffic, and LSAN zoning is used to enable the Fibre Channel Routingfeature of the MP Router to allow these devices to communicate across the FCIP Link as if they were inthe same fabric.

This configuration is a better solution than the Continuous Access two-fabric LSAN replication zonesolution because there is “No Single Point of Failure” (NSOF) as both the local and remote sites implementdual redundant fabrics and a separate FCIP link for each fabric pair. Still, the IP networks are part of theremote site fabrics and the backbone fabrics are the ones on the local site.


Figure 8 Continuous Access EVA 4–fabric FCIP router configuration

The design of a Meta SAN using FCIP needs to balance the scaling limitations of the backbone fabric withthe disruptions an IP network can have on the edge fabric. There are two alternative solutions to overcomethese two issues. The traditional solution has been to create a dedicated replication fabric or fabrics asshown in the five-fabric, and six-fabric implementations in Figure 9 and Figure 10. The other possiblesolution is to use a dedicated backbone fabric solution as shown in the six-fabric with dedicated BackboneFabrics implementation in Figure 11. This configuration is a modification of the four-fabric solution, wherethe functionality of the backbone fabric is removed from both the local and remote site fabrics and anew dedicated fabric is created for the Backbone. Both solutions eliminate the scaling limitations onboth sites, and the IP network only affects the replication traffic. The dedicated backbone fabric hastwo advantages over the dedicated Replication Fabric solution. It is more scalable and allows devicesother than the EVA storage connected to this dedicated Replication Fabric to communicate if needed.

Figure 9 shows a typical 2-port EVA 6000/5000/4000/3000 configuration of a Continuous Accessfive-fabric solution. In this configuration, a dedicated fabric is implemented for replication traffic, thuseliminating the fabric merging issue with a traditional FCIP implementation and the scaling limitationof an integrated backbone fabric solution. Half the EVA controller ports are connected to a dedicatedreplication fabric. Since the only devices in this replication fabric are the replication ports of the localand remote site, Fibre Channel Routing is not required. The benefit of the MP Router over traditionalFCIP gateways is that it eliminates the need for a separate Fibre Channel switch, as the MP Routerhas both capabilities in one device.


Figure 9 Continuous Access EVA five-fabric FCIP-router configurationFigure 10 shows a combination of a 4-port EVA 8000 and 2-port EVA 6000/5000/4000/3000configuration of a Continuous Access six-fabric solution. In this configuration, two dedicated fabricsare implemented for replication traffic. It eliminates the fabric merging issue with a traditional FCIPimplementation and the scaling limitation of an integrated backbone fabric solution. Half the EVAcontroller ports are connected to each dedicated replication fabric. Since the only devices in thisreplication fabric are the replication ports of the local and remote site, Fibre Channel Routing is notrequired. The benefit of the MP Router over traditional FCIP gateways is that it eliminates the need for aseparate Fibre Channel switch as the MP Router has both capabilities in one device.

NOTE:HP recommends that the primary or local site in this configuration be a 4-port EVA 8000 and thesecondary or remote site can be either a 4-port EVA 8000 or 2-port EVA 6000/4000/5000/3000.


Figure 10 Continuous Access EVA 6–fabric FCIP router configuration

Figure 11 shows a typical 4-port EVA 8000 configuration of a Continuous Access six-fabric with dedicatedbackbone fabrics LSAN replication zones solution. In this configuration, half the EVA controller portsare connected to each of the dual redundant fabrics for each site.

This configuration, using two dedicated backbone fabrics for Fibre Channel routing traffic betweenedge fabrics, solves all the issues with a traditional FCIP “implementation” and the scaling limitationsof an integrated backbone fabric solution. Fibre Channel Routing solves the issues associated with themerger of two physically separate fabrics. Since the backbone fabric is no longer used for local traffic,the scaling issues in terms of number of devices and switches in the fabric are mitigated. Also becausethe IP network is now part of the backbone fabric and not part of the local or remote fabrics, fabricdisruptions are minimized on these fabrics. This solution allows more than two sites to be connected tothe dedicated backbone fabrics, and so the same backbone fabric could be used for a primary site toconnect to multiple secondary sites.

This configuration also has the advantage of being able to share more devices than the dedicatedreplication fabrics, as the dedicated replication fabrics only have the EVA ports connected to them andonly the storage controller can communicate over these fabrics. This enables a server to connect tostorage resources on both the local and remote fabrics while maintaining the ease of management andfault isolation that two smaller physically separate fabrics have over one large merged fabric.


Figure 11 Continuous Access EVA six-fabric FCIP-router with dedicated backbonefabrics configuration

If your topology does not fit the sample configurations in this section, see the HP StorageWorks SANdesign reference guide on the website http://www.hp.com/go/sandesignguide for configurationrequirements and design considerations.

Overall Setup Plan

To set up Continuous Access replication from one B-Series fabric to another (FOS 5.2.1b or later) usingFibre Channel Routing and FCIP across a wide area connection:

1. Obtain both local and remote site IP addresses for the FCIP connection, and ensure that a staticroute is defined across the WAN.














2. Use B-Series WANTOOLS facilities to discover the operational characteristicsof the IP network you intend to use for Continuous Access replication. SeeTools for managing and monitoring the replication network, page 37 for more information.

Document the characteristics of the WAN connection including:

• Bandwidth available• PMTU—Path Maximum Transmission Unit and whether jumbo frames are supported across

the WAN (PMTU must be larger than 1500)

NOTE:If you input the wrong MTU size (too large), the I/O will take more time than necessary asthe IP transport (WAN link) makes no effort to optimize the transfer of data.

3. Install both local and remote B-Series MP routers (Director blade or stand-alone).

4. Enable/configure the B-Series MP Router ports for both FC connectivity to the local fabrics and GbE/ FCIP operation across the wide area connection.

5. Activate the FCIP link.

6. Define LSAN zones in both fabrics.

7. Configure B-Series 400 MP Router or MP Router blade ports for FC-FC routing by assigning theappropriate operational mode to the FC ports (either E_Port or EX_Port mode), and the GbE ports(either VE_Port or VEX_Port). There is no single right answer for this; each installation will have itsown operational requirements and considerations.

8. Connect the local and remote fabrics to the B-Series MP Router(s).

9. Run Continuous Access™ software to configure local and remote storage and replicate data.


4 Solution setup

Configuring FCIP on the HP StorageWorks 400 MP Router/MPRouter blade

Use the Web Tools interface to configure the FCIP connection between two geographicallyseparate sites on a Wide Area Network (WAN). You can also use the com-mand line interface with either direct console (serial) connection to the switch or through telnet sessions (seeConfiguring FCIP interfaces and tunnels on the HP StorageWorks 400MP Router using CLI commands, page 47in the Appendix.) Refer to the FOS 5.1.x (or later) administrator’s guide for additional information.

NOTE:It is assumed that the initial switch configuration setup steps are done, including the definition of SwitchName, IP/Subnet/Gateway (for switch management), Switch Domain ID, Time Zone, Date/Time, and soforth for all switches and directors in both the local and remote fabrics. See the HP StorageWorks FabricOS administrator’s guide for specifics on setting up the switch configuration.

Follow these steps to configure FCIP on the B-Series 400 MP router.

1. Start a browser.

2. In the address area, enter the IP address of the 400 MP Router to configure.

The switch login applet launches.

3. Enter the username and password.

The Web Tools interface displays.

4. Click ge0 on the GigE port.

The Port Administration Services window displays.


5. Ensure that port ge0 is selected and click Edit Configuration to launch the GigE Port ConfigurationWizard.

6. Click Next.

The GigE Port # 0 Configuration window displays.

7. Click Add Interface, and enter the IP address and MTU size.

Valid entries are 1500 and 2250.

NOTE:Your network administrator will provide the MTU size.

Table 7 FCIP configuration

Examples GbE Port IP Address (local) IP Address (remote) Tunnel

First Tunnel Ge0 10.0.10.1 10.0.10.2 0

8. Select Close > Next.

The Configure IP Routes window displays. A default route is added automatically.

9. Click Add Route and enter a new IP route.

10. Select Add > Close > Next.

The Select Tunnel window displays.

11. Select the tunnel to configure and click Next.

30 Solution setup

The FCIP Tunnel Configuration window displays.

12. Set the desired configuration parameters and click Next.

NOTE:If you want to enable compression across the FCIP link, click the Enable Compressioncheckbox in the Tunnel Configurations window. Do not select the FastWrite checkbox as HPContinuous Access EVA uses other ways to do this.Since it is a hardware-enabled compression, HP recommends enabling compression. HPalso recommends using committed tunnels.

13. Confirm your selections and click Finish to create the tunnel.

The Confirmation and Save Window displays. You have successfully created a tunnel.

14. Click Close.

15. Open another browser window and then open the Web Tools Switch View on the Remote 400MP Router.

16. Complete steps 4 through 14 to configure the 400 MP Router at the remote site.

The FCIP link setup is complete.

NOTE:When configuring the second MP Router, the local and remote IP addresses will be relativeto the machine you are on. You will need to reverse them when configuring the secondrouter.

17. Enable FCIP ports after both the local and remote FCIP configurations are complete.

a. From the Port Administrations window (it should still be open), click FC Ports.

b. Select the port to enable and then select Persistent Enable.

NOTE:Each GbE port on the router can have up to eight FCIP tunnels and up to eight logical VE_Ports oreight logical VEX_Ports, which correspond to logical FC ports. Table 8 shows the port mapping.

Table 8 Port mapping

Physical Ports Tunnels Virtual ports

ge0 0 through 7 16 through 23

ge1 0 through 7 24 through 31

c. Enable the FCIP port on the remote router.

NOTE:It can take Web Tools a while to update the FCIP changes. You can monitor the FCIPTunnels tab on the Port Administration Services window for link status.

NOTE:When you setup an FCIP tunnel (for FCR – Fibre Channel routing), ensure that the FC ports(0 – 15) are disabled. This prevents unintended fabric merges.


NOTE:Although not covered here, the procedures for the MP Router blades are identical, but somescreen shots will differ slightly given the blade orientation in the director chassis. To startthis procedure on a blade router, point your browser to the IP address of the Director.

Configuring Fibre Channel routing (FCR)To configure the Fibre Channel routing using Web Tools:

1. Launch the FC routing module via the FCR button in the Switch View on the router.

A tabbed interface displays, from which you can access the functions required to enable FCRon the switch you are connected to.

2. Ensure that the backbone fabric ID of the switch is the same as other FCRs in the backbone fabric.

• Click Set Fabric ID and either enter the FID value or select it from the drop-down menu.

3. Enable Fibre Channel routing (FCR).

a. Click Enable FCR.

b. Click Yes to confirm.

4. Ensure that the ports to configure as EX-Ports are not connected or are disabled.

5. Configure the EX-Ports:

a. Click the EX-Ports tab.

b. Select New to launch the EX-Port Configuration wizard.

c. Select the port to be configured. For this example, select port 0 and click Next to continue.

d. Set the Port Parameters (FID) and Interop mode; set the FC operational parameters.

e. Confirm the settings.

6. Connect the EX-Ports to the proper edge fabric if they are not already connected:

a. Connect the cables. Do not enable the ports yet.

b. Close the FCR Admin window.

7. Configure LSAN zones on the fabrics that share devices using the Zone Administration module ofWeb Tools:

a. Use the browser to launch the Switch View on the edge fabric switch.

b. Click zone admin to launch the Zone Administration module .

32 Solution setup

NOTE:LSANs are set up the same way as other zones with the exception that the zone namestarts with “LSAN_”.

NOTE:The Share Devices wizard in Fabric Manager simplifies the process of setting up LSANs.See HP StorageWorks Fabric Manager, page 50 for details.

8. The ports need to be enabled to see the LSANs. From the router, launch Web Tools and select theport to launch the Port Administration window:

a. Select the port and click Persistent Enable.

b. Close the Port Administrations window.

9. Click the FCR button on the Switch View to bring up the FCR module.

Use the tabs to view the EX-Ports, LSAN Fabrics, LSAN Zones and LSAN Devices and make sure thatthe configuration succeeded.

HP StorageWorks Continuous Access configuration procedureHP StorageWorks Continuous Access EVA software is an array-based application that utilizes a powerfulsimple graphical user interface to create, manage and configure remote replication on the entire EVAproduct family. Continuous Access EVA shares an integrated management interface, called ReplicationSolutions Manager™ (RSM), with HP StorageWorks Business Copy™ offering a unique, unifiedreplication management approach.

Refer to online Continuous Access EVA reference manuals for detailed planning and configurationinformation at http://www.hp.com/go/caeva .

The following includes some of the array-specific factors to be aware of while configuring the ContinuousAccess replication solution:

Disk groupWhen data is synchronously replicated remotely, application performance is not necessarily improvedby increasing the number of disks in a disk group. This is because response time for application writesincludes the time for replication. In addition, sequential access (read or write) is limited by the per-diskperformance rather than the number of disks in the disk group. Additional disks improve response timeonly when an application has a high percentage of random reads compared to writes.

Analyze the I/O profile of your applications and consider the following:

• If the application I/O stream is dominated by a mix of simultaneous sequential and randomtransfers, determine how these streams can be directed to specific virtual disks.

• Put virtual disks with similar tasks in the same disk group. In general, separate sequential I/Ostream data (database logs, rich content) from random I/O streams (database information store,file shares).

Transfer profiles that differ over time are not a concern. A virtual disk that receives sequential transfers forpart of the day and random accesses for the rest of the day will operate well in both cases. The issue toconsider is accommodating simultaneous sequential and random streams.

DR groupsA data replication (DR) group is a logical group of virtual disks in a remote replication relationship with acorresponding group on another array. Hosts write data to the virtual disks in the source DR group, and














the array copies the data to the virtual disks in the destination DR group. Virtual disks in a DR group failover together, share a write history log (DR group log), and preserve write order within the group.

Virtual disks that contain data for one application must be in one DR group. For optimum failoverperformance, limit the virtual disks in a DR group to as few as possible, and do not group virtual disksthat are assigned to separate applications.

The maximum number of virtual disks in a DR group and the maximum number of DR groups per arrayvary with controller software versions. For current supported limits, see the latest HP StorageWorks EVAreplication software consolidated release notes.

DR group logPlan for the additional disk space required for DR group logs. A DR group stores data in the DR grouplog when:

• A problem occurs with the intersite link• In suspended mode• Using enhanced asynchronous write mode

The log requires Vraid1 space ranging from 136 MB to 2 TB, with the maximum value depending onthe size of the DR group members and the version of controller software. (In later versions, you canspecify the maximum DR group log size.) For version support, see HP StorageWorks EVA replicationsoftware consolidated release notes at the manuals location mentioned above. If XCS 6.0 or later isbeing used, create the DR group log on an online drive. Constant writes to the DR group log in enhancedasynchronous mode significantly shortens the expected lifetime of near on-line drives.

HP cluster technologies for disaster-tolerant solutionsHP offers a comprehensive portfolio of disaster-tolerant solutions to protect the customer’s data inthe event of disaster or system failure. Clustering technologies can be deployed in order to provideautomatic application failover and failback capabilities. This section will provide an overview of possibletechnologies. All are built on the foundation of HP’s clustering software, HP Serviceguard™.

HP ServiceguardHP Serviceguard™ is a high availability (HA) clustering solution that leverages the strength of HP’sexperience in the HA business, bringing the best-in-class mission critical HP-UX technologies to the Linuxenvironment and Proliant and Integrity servers. The cluster kit includes high availability software thatenterprise customers require for 24x7 business operations.

It is designed to:

• Protect applications from a wide variety of software and hardware failures• Monitor the health of each server (node)• Quickly respond to failures, including system processes, system memory, LAN media and

adapters, and application processes• Enable customers to cluster HP Proliant and Integrity server families with a choice of shared

storage, depending on requirements

For more information, see the website http://www.hp.com/go/ha.

HP Storageworks Cluster Extension EVAHP StorageWorks Cluster Extension EVA™ offers protection against application downtime from fault,failure, or site disaster by extending a local cluster between data centers over metropolitan distances.CLX EVA integrates with open-system clustering software (Microsoft Cluster Service in the Windows2003 environments and HP Serviceguard™ for Linux in Red Hat and SuSe Linux environments) andHP StorageWorks Continuous Access EVA™ to automate failover and failback between sites. ClusterExtension EVA™ delivers true hands-free failover/failback decision making - in the event the human

34 Solution setup

http://www.hp.com/go/ha












storage administrator is unaware of the outage, unable to respond or not present - because ClusterExtension EVA™ requires no server reboots or LUN presentation/mapping changes during failover.

HP StorageWorks Cluster Extension EVA™ software is an integrated solution that provides protectionagainst system downtime with automatic failover of application services and read/write enabling ofremotely mirrored mid-range storage over metropolitan distances. Cluster Extension EVA ™adapts in realtime, to real life situations, providing protection via rapid site recovery. Cluster Extension EVA ™deliverstrue hands-free failover/failback decision making - in the event the human storage administrator isunaware of the outage, unable to respond or not present - because Cluster Extension EVA requires noserver reboots or LUN presentation/mapping changes during failover.

Cluster Extension EVA integration provides efficiency that preserves operations and delivers investmentprotection as it monitors and recovers disk pair synchronization on an application level and offloads datareplication tasks from the host. Cluster Extension EVA supports the entire EVA family of arrays at eitherthe primary or secondary site. Implementation of a Cluster Extension EVA solution assures the higheststandards in data integrity by maximizing the advantages of its integration with Continuous Access EVASoftware, and with HP Serviceguard for Linux in Red Hat and SuSe Linux environments and MicrosoftCluster Service in Windows 2003 environments.

For more information, see http://www.hp.com/go/clxeva.

HP Metrocluster/HP ContinentalclustersHP Metrocluster and HP Continentalclusters are disaster-tolerant solutions for the HP-UX 11i environment.Both are built on HP’s foundation clustering software, HP Serviceguard, providing the highest level ofavailability and business continuity for enterprise data centers. Both are integrated with ContinuousAccess EVA. HP Metrocluster is a business continuity solution with automatic site failover for up to 16 HPIntegrity or HP 9000 servers connected to array-based storage. It provides automatic and bi-directionalfailover of business-critical data and applications located at data centers up to 300km apart, so bothdata centers can be active, protected, and capable of handling application failover for each other. HPContinentalclusters is HP’s disaster-tolerant solution for unlimited distances. Since there are no distancelimitations on how far apart the data centers can be located, Continentalclusters provides flexibility forcustomers in where to locate their computing resources. It provides both manual and bi-directional failoverof business-critical data and applications over unlimited distance.

For more information, see http://www.hp.com/go/dt.


http://www.hp.com/go/clxeva












http://www.hp.com/go/dt












36 Solution setup

5 Tools for managing andmonitoring the replication network

Sizing link bandwidth requirements for remote replication is critical in meeting customer’s expectations.This section includes tools that can be used for estimating the effects of inter-site latency as well asdetermining the characteristics of the inter-site link. For additional information about calculating latencyand estimating bandwidth requirements, see the HP StorageWorks Continuous Access planning guideand the HP StorageWorks Continuous Access EVA Performance Estimator user guide. Both the planningguide and estimator user guide can be found via the Technical Documents link on the Continuous AccessEVA homepage at http://www.hp.com/go/caeva.

HP StorageWorks Continuous Access EVA PerformanceEstimator

HP StorageWorks Continuous Access EVA Performance Estimator (the estimator) is an interactivespreadsheet that calculates the approximate effect of inter-site latency and available bandwidth onreplication throughput for specific link technologies and application write size. You supply the latencyand application writes size, and the estimator determines the average replication I/Os per second(IOPS) and throughput.

You can use the estimator to evaluate:

• The performance capabilities of specific inter-site links• The link requirements for specific levels of performance• The bandwidth and time required for a full copy of the source disks

Downloading the estimator1. Browse to the HP StorageWorks Continuous Access EVA website http://www.hp.com/go/caeva.

2. Click Related Information.

The related information links are displayed

3. Click HP StorageWorks Continuous Access EVA Performance Estimator.

4. In the File Download dialog box, click Save and select the destination for the file

5. To use the estimator, open the file in Microsoft Excel.

The first time you open the Excel file, the default values display. Values in the boxes with whitebackground can be changed.


























Figure 12 HP StorageWorks Continuous Access EVA Replication PerformanceEstimator-V3

Solution testing with EVA workloadsDuring acceptance testing and post installation, it is very important to monitor the network under a varietyof representative Continuous Access EVA workloads before placing the system in production. Some or allof these tests should be run concurrently. Suggested workloads include the following:

• Full DR Group copies (normalization of volumes). At least four operating concurrently isrecommended

• Local I/O between host initiators and EVA Storage Arrays• Replication• Tape Backup

Various tools which can used to gather information are:

• Host Tools: PERFMON, IOSTAT or a similar performance tool• EVA Tools: Continuous Access EVA Performance Estimator, EVA-PERF

HP StorageWorks B-Series toolsA basic Ethernet MTU is 1518 bytes. This forces an FC frame to be broken into two Ethernet packetswhen traveling via FCIP. A 2250 byte jumbo packet can accept an entire standard FC frame (2148 bytes)leading to improved FCIP performance and more efficient network utilization. Many IP service providerscan support jumbo packets throughout their network.

It is critical that the user understands the operational characteristics of the IP link intended to be usedfor the FCIP communications. WAN analysis tools are designed to estimate the end-to-end IP pathperformance characteristics between a pair of FCIP port endpoints. WAN tools include the followingcommands and options:

38 Tools for managing and monitoring the replication network

• portcmd ipperf—Characterizes end-to-end IP path performance between a pair of B-SeriesFCIP ports. The path characterization elements include:• Bandwidth—Total packets and bytes sent. Bytes/second estimate will be maintained as a

weighted average with a 30 second sampling frequency and also as an average rate over theentire test run.

• Loss—Estimate is based on the number of TCP retransmits (assumption is that the number ofspurious retransmits is minimal). Loss rate (percentage) is calculated based on the rate ofretransmissions within the last display interval.

• Delay/Round Trip Time (RTT)—TCP smoothed RTT and variance estimate in milliseconds.• Path MTU (PMTU)—Largest IP-layer datagram that can be transmitted over the end-to-end

path without fragmentation. This value is measured in bytes and includes the IP headerand payload. There is limited support for black hole PMTU discovery. If the Jumbo PMTU(anything over 1500) does not work, ipperf will try 1500 bytes (minimum PMTU supportedfor FCIP tunnels). If 1500 PMTU fails, ipperf will give up. There is no support for aging.PMTU detection is not supported for active tunnels. During black hole PMTU discovery, theBW, Loss, and PMTU values printed might not be accurate.

• portshow fcipTunnel—Displays performance statistics generated from the WAN analysis.

WAN analysis toolsTypically, you start the WAN tool before setting up a new FCIP tunnel between the two sites. You canconfigure and use the ipperf option immediately after installing the IP configuration on the FCIP port.Once the basic IP addressing and IP connectivity is established between two sites, you can configureipperf with parameters similar to what will be used when the FCIP tunnel is configured.

The traffic stream generated by the WAN tool ipperf session can be used to:

• Validate a service provider Service Level Agreement (SLA) throughput, loss, and delaycharacteristics

• Validate end-to-end PMTU, especially if you are trying to eliminate TCP segmentation of largeFibre Channel frames

• Study the effects and impact FCIP tunnel traffic may have on any other applications sharingnetwork resources

Procedure description1. A telnet session is used to connect to the local and remote B-Series Routers and define the IP

interface address to use with the GbE ports on each router. If more than one FCIP tunnel is used,it is necessary to define a local and remote address for each tunnel. This is accomplished usingthe FOS command portcfg. These addresses will be routable across the client IP network andwould have been provided from the client IP network administrator.

2. After the IP address interfaces have been defined, the user can verify that the IP addresses areroutable and reachable by using the B-Series FOS command portcmd with the command controlparameter —ping.

3. With routable connection established and tested with the “ping” step, the user will connect to theremote B-Series router and use the FOS command portcmd with the command control parameter-ipperf to prepare the remote device for the WANTOOLS diagnostic process. This is known asspecifying the sink mode to accept the new connection and is accomplished with the -R parameterof the ipperf command. There are additional parameters required, including -s and -d, tospecify the ip address of the source and destination router.

4. Next the user returns to the local B-Series router and uses portcmd with the command controlparameter -ipperf to specify the local machine as the source mode to initiate the TCP connection.The source end-point generates a traffic stream and reports to the end-to-end IP path characteristicsfrom this end-point toward the receiver end-point sink. This step is accomplished with the ipperfcommand parameter -S. There are additional parameters required including −s and −d to specifythe IP address of the source and destination router, plus a test duration -t (time to run test: default isforever) and -i (display/refresh interval, default: 30) specified in seconds.


5. Using the output from these commands, the user has data that can be evaluated and used to guidethe configuration of the FCIP tunnel.

CLI syntaxportcmd

ping: Pings a destination IP address from one of the source IP interfaces on the GbE port.

Usage portcmd --ping [slot/]port args

Arguments -s src_ipSpecifies the local IP address to use for sourcing theprobe packets-d dst_ipSpecifies the destination IP address to probe the IP routerpath

Optional arguments -n num_requestsSpecifies the number of ping requests. The default is 4.This operand is optional.-q service_typeSpecifies the type of service in the ping request. Thedefault is 0 and service_type must be an integer from 0to 244. This operand is optional.-t ttlSpecifies the time to live. The default is 100. Thisoperand is optional.-w wait_timeSpecifies the time to wait for the response of eachping request. The default is 5000 milliseconds and themaximum wait time is 9000. This operand is optional.-z sizeSpecifies the default packet size to a fixed size in bytes.The default is 64 bytes. The total size, including ICMP/IPheaders (28 bytes without IP options), cannot be greaterthan the IP MTU configured on the interface. Thisoperand is optional.

ipperf: Determines the path characteristics to the remote host.

Usage portcmd --ipperf [slot/]geport args [optional_args]

Arguments -s src_ipSpecifies the local IP address to use for sourcing theprobe packets. ipperf will not start if an IPSec-enabledtunnel using the same source IP address exists-d dst_ipSpecifies the destination IP address to probe the IP routerpath.-SSpecifies the source mode to initiate the TCP connection.-RSpecifies the sink mode to accept the new connection.The end-to-end path characteristics are not reported.

Optional arguments -r committed_rateSpecifies the committed rate for the data stream inkilobits/sec (kbps)-i interval


Specifies the display/ refresh interval in seconds.Default: 30 sec-p portSpecifies the TCP port number for the listener end-point.Default: 3227-t running_timeSpecifies how long to run the test, in seconds. Default:run forever-z sizeSpecifies the default packet size in bytes. Default: 64bytes

Examples1. To verify if packets can be sent to the destination IP address, enter:

portcmd --ping 4/ge0 -s 192.168.100.50 -d 192.168.100.402. To prepare the Remote B-Series router GbE port to receive (sink), enter:

portcmd --ipperf ge0 –s 192.168.100.40 –d 192.168.100.50 –R3. To execute the WANTOOLS procedure from the Local B-Series Router GbE port to the Remote

GbE port, collect data for a period of 60 seconds, and sample at an interval of 5 seconds, enter:portcmd --ipperf ge0 –s 192.168.100.40 –d 192.168.100.50 –S –i 5 –t 60

NOTE:1. In the above examples, the source and destination IP addresses are specified in the context of

where the command is executed. When connected via a telnet session to the local site router, thesource (-s) is the IP address of the interface of the local router and the destination (-d) is theFCIP interface address on the remote router.

2. There are optional parameters for the -ipperf command that can be used to further characterizethe link and test other IP ports. Only a sampling of simple usage are shown.

CLI syntax:portshow

fciptunnelTo view the performance statistics and monitor the behavior of an online FCIP tunnel:

Usage portshow fciptunnel [slot/]geport args[optional_args]

Arguments all | tunnel_idShows all or tunnel_id FCIP tunnels on this GbEport

Optional arguments -perfShows additional performance information-paramsShows connection parameter information

ExamplesExecuting portshow fciptunnel 8/ge0 0 −perf displays the following output:


Executing portshow fciptunnel 8/ge0 0 −params displays the following output:


6 Related information

This document covers FCIP disaster recovery solutions using the B-Series components. However, additionaltechnologies are also supported. These include using native Fibre Channel with WDM technology, andContinuous Access XP. Both of these technologies are supported with the B-Series components.

Dark Fiber/WDMBesides extension over FCIP, the 400 MP Router and MP Router blade are supported with other types ofSAN extension technology:

• Native Fibre Channel—This choice is based on direct Fibre Channel extension using short orlong-wavelength, small form pluggable (SFPs) and Dark Fiber. Distance support is dependent onthe SFP range, but is usually below 50km. With this option, the performance is the best possible,both in term of latency and throughput. Cost varies from “low” for short runs using multi-modefiber optic (MMF) cables and short wavelength (SWL) media, to “high” using single-mode fiberoptic (SMF) cables and long wavelength (LWL and ELWL) transceivers. Compared to otherextension options, LWL transceivers are inexpensive and easy to deploy. This SAN extensionoption does have two drawbacks: limited distances are supportable and the cost of fiber runs.Dedicated dark fiber links are used for every port of bandwidth required, and the dark fibercables themselves can be expensive.

• Native Fibre Channel with Wavelength Division Multiplexing (WDM)−SAN extension utilizingWDM (either DWDM or CWDM) through an existing optical metropolitan area network (MAN),which can handle multiple protocols. Distances range from 50 km up to hundreds of kilometers.CWDM is lower cost than DWDM, which offers longer distances. Both CWDM (8 Wave-lengths)& DWDM (32 Wave-Lengths) offer the benefit of multiple wavelengths of light over a singlefiber optic cable for increased link capacity.

For more details on these SAN extension technologies with B-Series fabrics, see the SAN extensionssection of HP StorageWorks SAN design reference guide at http://www.hp.com/go/sandesignguide.

XP array family and Continuous Access XPThe 400 MP Router and MP Router Blade can also be used in a disaster recovery solution usingContinuous Access XP and the XP family of storage arrays (XP10000/XP12000). The HP StorageWorksXP10000 Disk Array, an entry-level high-end array, delivers always-on availability for mission-critical ITenvironments. Boot-once scalability and heterogeneous connectivity in a compact footprint increasesbusiness agility and decreases the stress of running applications where downtime is not an option. TheHP StorageWorks XP12000 Disk Array is an enterprise class storage system that delivers state-of-the-artreliability and always-on availability for mission-critical applications where downtime is not an option.Both the XP10000 and the XP12000 are designed for organizations that demand the most from theirstorage. Complete redundancy throughout the architecture provides no single point of failure, andnon-disruptive online upgrades ensure that data is always available. HP StorageWorks ContinuousAccess XP software products are high availability data and disaster recovery solutions that deliverhost-independent, real-time, remote data mirroring between XP disk arrays. With seamless integrationinto a full spectrum of remote mirroring based solutions, these products can be deployed in solutionsranging from data migration to high availability server clustering.

For more information on Continuous Access XP software, see http://www.hp.com/go/storageworks/software.

For more information on XP disk arrays, see http://www.hp.com/go/storage/xparrays.














http://www.hp.com/go/storageworks/software
















http://www.hp.com/go/storage/xparrays















46 Related information

7 Appendix:

Configuring FCIP interfaces and tunnels on the HPStorageWorks 400 MP Router using CLI commands

This section is for expert users.

Command procedure description1. The user will use a telnet session to connect (login) to the local and remote B-Series routers.

2. Ensure that both the FC and FCIP ports are disabled during configuration operations. This preventsunintended fabric merges between local and remote fabrics.

3. By default, virtual ports are created as VE_Ports. If a VEX_Port is desired, use portcfgvexportto configure the port.

4. Use the command portcfg to configure the GbE port, IP interfaces on the GbE port, static routeson the IP interface, and FCIP tunnels.

a. Define the IP interface of each virtual port.

b. Add IP routes on a GbE port, i.e., create the static IP route.

c. Configure the FCIP tunnel.

CLI syntaxportcfgvexport

Configure VEX_Ports

Usage portcfgvexport [slot/]port args

Arguments -a adminSpecify 1 to enable or 2 to disable the admin.-f fabricidSpecify 1 to 128 for the fabric ID.-d domainidSpecify 1 to 239 for the preferred domain ID.-p pidformatSpecify 1 for core, 2 for extended edge, and 3 for nativeport ID format.-t fabric_parameterSpecify 1 to enable or 2 to disable negotiate fabricparameters.


portcfg

Configures the FCIP interfaces and tunnels.

ipif: Configure IP interface entries

Usage portcfg ipif [slot/][ge]port args

Arguments create ipaddr netmask mtu_sizeCreates IP interfacesdelete ipaddrDeletes IP interfaces.

iproute: Configure IP route entries

Usage portcfg iproute [slot/][ge]port args.

Arguments create ipaddr netmask gateway_router metricCreates IP routes.delete ipaddr netmaskDeletes IP routes.

fciptunnel: FCIP tunnels

Usage portcfg fciptunnel [slot/][ge]port args [optional_args].

Arguments create tunnel_id remote_ipaddr local_ipaddr comm_rateCreates FCIP tunnels.

Optional arguments -cEnables compression on the tunnel specified.-f fastwriteEnables fastwrite on the tunnel specified. This argumentcannot be used together with -ike, -ipsec or -key (IPSec).-ike policySpecifies the IKE policy number used on the tunnelspecified. This argument must be used with -ipsec and-key. This argument cannot be used together with -f(fastwrite) or -t (tape pipelining).-ipsec policySpecifies the IPSec policy number to be used on thetunnel specified. This argument must be used togetherwith -ike and -key. This argument cannot be usedtogether with -f (fastwrite) or -t (tape pipelining).-k timeoutSpecifies the keep alive timeout, in seconds. timeoutvalues are 8 to 7,200; default is 10. If tape pipelining isenabled, minimum value supported is 80.-key preshared-keySpecifies the preshared-key to be used during IKEauthentication. The maximum length is 32 bytes. It mustbe a double quoted string of alpha-numeric characters.The value of this key must be at least 12 bytes. Thisargument must be used together with -ike and -ipsec.This argument cannot be used together with -f (fastwrite)or -t (tape pipelining).-m timeSpecifies the minimum retransmit time, in milliseconds.time values are 20 to 5,000; default is 100.-n remote_wwnSpecifies the remote-side FC entity WWN.

48 Appendix:

-r retransmissionsSpecifies the maximum retransmissions. Retransmissionsvalues are 1 to 8; default is 8. If tape pipelining isenabled, the default value is calculated based on theminimum retransmit time to ensure that tcp connectiondoes not timeout before the host times out. If the userchanges this value, the value specified must be greaterthan the calculated value.-sDisables selective acknowledgement code (SACK) onthe tunnel specified.-tEnables tape pipelining on the tunnel specified (requiresfastwrite to be turned on). This argument cannot be usedtogether with -ike, -ipsec or -key (IPSec).

NOTE:Only a single IPSec-enabled tunnel can beconfigured on a port. No other tunnels (IPSecor otherwise) can be configured on the sameport. Jumbo frames will not be supportedon secure tunnels. Only a single route issupported on an interface with a securetunnel.

Arguments modify tunnel_idModifies the properties of the existing FCIP tunnel. Thiswill disrupt the traffic on the FCIP tunnel specified for abrief period of time. If the FCIP tunnel has IPSec enabled,it cannot be modified. To change it, you must delete itand recreate it.

OptionalArguments

-b comm_rateSpecifies the desired committed rate for the existingtunnel.-c 0|1Disable (0) or Enable (1) compression on the existingtunnel.-f 0|1Disable (0) or Enable (1) fastwrite on the existing tunnel.-k timeoutSpecifies the keep alive timeout, in seconds, for theexisting tunnel. timeout values are 8 to 7,200; default is10. If tape pipelining is enabled, the minimum valueis 80.-m timeSpecifies the minimum retransmit time, in milliseconds,for the existing tunnel. time values are 20 to 5,000;default is 100.-r retransmissionsSpecifies the maximum retransmission for the existingtunnel. retransmission values are 1 to 16; default is 8. Iftape pipelining is enabled, the default value is calculatedbased on the minimum retransmit time to ensure that tcpconnection does not timeout before the host times out. Ifthe user changes this value, the value specified must begreater than the calculated value.-s 0|1


Disable (0) or Enable (1) selective acknowledgement(SACK) on the existing tunnel.-t 0|1Disable (0) or Enable (1) tape pipelining

NOTE:Some of the optional portcfg commandsettings are not compatible with the HPStorageWorks Continuous Access EVAproduct.

Examples1. To configure a VEX_Port, enter:

portcfgvexport 8/18 -a 1 -f 2 -d 2202. To create an IP interface, enter:

portcfg ipif ge0 create 192.168.100.50 255.255.255.0 1500Verify the created IP interface:portshow ipif ge0

3. To create a static IP route, enter:portcfg iproute ge0 create 192.168.11.0 255.255.255.0 192.168.100.1 1Verify the route has been successfully created:portshow iproute ge0

4. To create an FCIP tunnel, enter:portcfg fciptunnel ge0 create 2 192.168.100.40 192.168.100.50 10000

HP StorageWorks Fabric ManagerHP StorageWorks Fabric Manager is a highly scalable, Java-based application that manages multipleB-series switches and fabrics in real time. In particular, Fabric Manager provides the essential functionsfor efficiently configuring, monitoring, dynamically provisioning, and managing SAN fabrics on a dailybasis. It is an optional software package for the B-Series SAN products. An evaluation copy is availablevia download from the HP Web Site.

To download an evaluation copy:

1. Browse to the HP StorageWorks Storage networking site http://www.hp.com/go/san

2. Select B-Series Switches > B-Series Software > HP StorageWorks Fabric Manager Software.

3. Download the evaluation version appropriate for your operating system.

HP StorageWorks Fabric Manager share devices wizardThe following is assumed:• Knowledge of Fabric Manager• Fabric Manager is installed• SAN fabrics in the enterprise are discovered

For the Multi-Protocol Router, this wizard walks the user through a series of steps to share devices betweenfabrics, and includes steps to connect the edge fabric to the FC Router. Without this, sharing deviceswould be a manual operation on multiple different fabrics. It collates information from multiple sources,analyzes information from different fabrics to present a comprehensive view, and provides information onthe FC Router, EX_Ports and LSANs.

Follow the steps below to set up LSANs using Fabric Manager:

1. Open Fabric Manager and select an edge fabric that will be part of the LSAN.

50 Appendix:













2. Select Tasks > Device Sharing and Troubleshooting > Share Devices to launch the Share Devicewizard.

3. Click Next.

The Select Devices to Share window displays.

4. Enter the logical SAN (LSAN) name.

In this example, the LSAN name is LSAN_CA_Replication; the local managed fabric Switch115 iswhere the first aliases containing device port WWNs are selected from. The ports include thehost port where Command View is run, and port number 4 from the EVA 8000 top and bottomcontrollers. The use of zoning aliases makes it easy to recognize the devices, rather than havingto read device World Wide Names.

5. Select the device to share from the Available Devices list and click the right arrow to move devicesto the Selected Devices list.

In this example, the EVA4000 devices are selected from the remote fabric names Switch37.

NOTE:The Remote Fabric called switch37 is visible to Fabric Manager, allowing easy selection of the devicesthat need to be available to Continuous Access EVA for the replication process.

6. Click Next.


7. Select Finish > Yes > Yes.

The LSAN is created.

Fabric Manager distributes the LSAN definitions to both Fabrics. This process may take a fewminutes, depending upon if the routed fabrics are local or across the WAN.

8. Select OK > Close to close the wizard.

Viewing LSANS using Fabric Manager• Choose an edge fabric and select Tasks > Device Sharing and Troubleshooting > Show LSAN view.

The devices in the LSAN LSAN_CA_Replication display.

52 Appendix: