INTEGRATING RECOVERPOINT FOR VIRTUAL MACHINES AND CISCO ACI

Transcription

1 INTEGRATING RECOVERPOINT FOR VIRTUAL MACHINES AND CISCO ACI Overview and configuration steps ABSTRACT This white paper provides describes how to properly setup a configuration consisting of Cisco ACI, VMware ESXi and RecoverPoint for Virtual Machines. EMC WHITE PAPER

2 To learn more about how EMC products, services, and solutions can help solve your business and IT challenges, contact your local representative or authorized reseller, visit or explore and compare products in the EMC Store Copyright 2016 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. VMware, ESX, ESXi, vcenter Server and NSX are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other trademarks used herein are the property of their respective owners. Part Number H

3 TABLE OF CONTENTS EXECUTIVE SUMMARY... 4 AUDIENCE... 4 ASSUMPTIONS... 4 TARGET TOPOLOGY... 5 Physical Topology... 5 Target Topology Additional Details... 5 Logical Topology... 6 Logical Topology additional details... 6 IP Address assignment... 7 OVERVIEW OF CONFIGURATION STEPS... 7 DETAILED CONFIGURATION STEPS... 7 ACI Configuration... 7 Create a VMM Domain... 9 Verify APIC to vcenter connectivity Verify vcenter to APIC connectivity Configure the Distributed vswitch in vcenter Create the rp4vm Networks via APIC Create VMM EPGs Create uplink epg Modify iscsi Port Groups to allow iscsi Configure vmknics and attach to iscsi Port Groups Install RP4VM During Deploy OVF Template

4 EXECUTIVE SUMMARY The RecoverPoint for Virtual Machines (RP4VM) installation process recommends that end users: 1. Pre-configure four network instances (i.e., LAN Network, WAN Network, iscsi1 Network and iscsi2 Network) on the ESX servers where RP4VM will be installed; and 2. Associate the four RP4VM network interfaces (i.e., LAN Interface, WAN Interface, iscsi1 Interface and iscsi2 Interface) to the pre-configured network instances. The first recommendation, pre-configuring the network instances, can be automated to a certain degree by using either VMWare NSX or Cisco Application Centric Infrastructure (Cisco ACI ). Of these two options, only Cisco ACI is currently capable of automating the creation of all network instances. VMware NSX is currently unable to create network instances that can be utilized by ESX vmkernel NICs. AUDIENCE This white paper is intended for anyone interested in using Cisco ACI to support the networking requirements for RecoverPoint for Virtual Machines (RP4VM) version 4.2 or 4.3. Future versions of RP4VM may provide additional scale and functionality. Please refer to the Installation and Deployment guide for the RP4VM version you are working with for further information. ASSUMPTIONS This white paper assumes: 1. ESXi has been installed on the servers that will be used for RP4VM and that all servers have been assigned an IP Address 2. The VM Network shown in the logical topology shown below has been created. 3. VMware vcenter Server has been installed and all servers are being managed by a single vcenter instance. Note: A single vcenter instance is being used for the sake of example only and is not a requirement. RP4VM 4.2 and 4.3 support up to four vcenters per RP4VM cluster and up to three RP4VM clusters in a system. 4. Cisco ACI has been physically installed and all leaf switches have been initialized and are visible in the APIC Fabric Topology view. 5. The Servers running ESX have been physically cabled to the Cisco ACI leaf switches as shown in the physical topology diagram below. 4

5 TARGET TOPOLOGY This white paper describes how to configure the following physical and logical topologies. Physical Topology Default Gateway: APIC: M C APIC (UCS 200) L1 L2 LAN x M Spine (Nexus 9336) C 1/16 M C M C Leaf1 (Nexus 9396) Leaf2 (Nexus 9396) 1/3 1/4 1/5 1/3 1/4 vmnic1 vmnic1 vmnic1 vmnic5 vmnic5 ESX1: ESX2: ESX3: ESX1: ESX2: Site A (VSAN_Cluster) Site B (TwoNode_Cluster) Target Topology Additional Details The LAN network for RP4VM will be provided via the ACI uplink from Leaf2 Interface 1/16. Although not shown in this diagram, a similar approach could be followed for the WAN link. 5

6 Logical Topology Site A - ESX 235 Site B - ESX 86 VM Test1 VM Network VMNIC2 VMNIC0 VM Network VM Test1.copy Splitter ESX iscsi Initiator DS XtremIO (VSAN_Cluster) XtremIO (TwoNode_Cluster) DS Splitter ESX iscsi Initiator Vmknic4 ( ) Vmknic3 ( ) PG iscsi1 PG iscsi2 PG WAN VMNIC 1 VMNIC 5 PG iscsi1 PG iscsi2 PG WAN Vmknic4 ( ) Vmknic3 ( ) vrpa j1 PG LAN VDS A PG LAN VDS B vrpa k1 vnic3 (iscsi tgt) vnic3 (iscsi tgt) vnic2 (iscsi tgt) vnic2 (iscsi tgt) vnic0 (WAN) vnic0 (WAN) vnic1 (LAN) vnic1 (LAN) Site A - ESX 236 VM Network LAN Site A iscsi1 Site A iscsi2 Site A WAN iscsi2 Site B iscsi1 Site B LAN Site B VM Network Site B - ESX 87 VM Test2 VM Network VMNIC2 VMNIC0 VM Network VM Test2.copy Splitter ESX iscsi Initiator DS XtremIO (VSAN_Cluster) XtremIO (TwoNode_Cluster) DS Splitter ESX iscsi Initiator Vmknic4 ( ) Vmknic3 ( ) PG iscsi1 PG iscsi2 PG WAN VMNIC 1 VMNIC 5 PG iscsi1 PG iscsi2 PG WAN Vmknic4 ( ) Vmknic3 ( ) vrpa j1 PG WAN VDS A PG LAN VDS B vrpa k1 vnic3 (iscsi tgt) vnic3 (iscsi tgt) vnic2 (iscsi tgt) vnic2 (iscsi tgt) vnic0 (WAN) vnic0 (WAN) vnic1 (LAN) vnic1 (LAN) Logical Topology additional details A couple of points worth noting: As explained in the Assumptions section above, it is assumed that the VM Network shown above in red has already been created. Although there is only a single WAN network shown above, you will actually create 2 WAN networks in the example below (one for Site A and another for Site B). The purpose for doing this is to provide a basic idea of how to work with contracts. We are using the ESXi Software based iscsi initiator for this example. Although it is not shown in the topology diagram above, we are connecting to the EMC XtremIO array via iscsi and are also making use of the ESXi software based iscsi initiator for this purpose. 6

7 IP Address assignment The following IP Addresses assignments will be used. OVERVIEW OF CONFIGURATION STEPS 1. ACI Configuration a. Configure Fabric b. Add vcenter to APIC c. Verify connectivity 2. vcenter Configuration a. Configure the Distributed vswitch in vcenter 3. Tenant (RP4VM network) Configuration a. Create the rp4vm Networks via APIC b. Modify iscsi Port Groups to allow iscsi via vcenter c. Configure vmknics and attach to iscsi Port Groups via vcenter d. Install RP4VM Appliance via vcenter DETAILED CONFIGURATION STEPS ACI CONFIGURATION Configure Fabric 1. Create three switch profiles; Leaf1, Leaf2, BothLeaves a. Under FABRIC -> ACCESS POLICIES, expand Switch Policies and then right click Profiles and click Create Switch Profile b. Provide a name (i.e., Leaf1) c. Click the + to add a Switch Selector i. Provide a name (i.e., Leaf1SwSel) Select the Leaf node ID of Leaf1 (i.e., 101) i iv. Click UPDATE Click NEXT v. Click FINISH d. Repeat Steps b and c but use a name of Leaf2, a switch selector name of Leaf2SwSel and select the Leaf Node ID of Leaf2 (i.e., 102). 7

8 e. Repeat Steps b and c but use a name of BothLeaves, a switch selector name of BothLeavesSwSel and select the Leaf Node IDs of Leaf1 and Leaf2 (i.e., 101 and 102). NOTE: This step is not technically required for this demo but Cisco recommends creating one by default. 2. Create an Attachable Access Entity Profile for the interface connected to the LAN. a. Under FABRIC -> ACCESS POLICIES, expand Global Policies and then right click Attachable Access Entity Profiles and click Create Attachable Access Entity Profile. i. Provide a name (i.e., ExternalNetwork) Click the + next to Domains (VMM, etc..) and then from the Domain Profile pull down, 1. Select Create Physical Domain a. Provide a name (i.e., Dell_Switch_Port16) b. Then from the VLAN Pool pull down, select create VLAN Pool i. Provide a name (i.e., UntaggedSwitch) Select the Dynamic Allocation radio button i Click the + next to encap blocks 1. Provide the starting VLAN ID (i.e., 99) 2. Provide the ending VLAN ID (i.e., 99) 3. Click OK iv. Click SUBMIT c. Click SUBMIT i Click UPDATE iv. Click NEXT and the ASSOCIATION TO INTERFACES dialog is displayed. v. Click the + under Select the interfaces and the CONFIGURE INTERFACE, PC, AND VPC dialog is displayed. 1. In the CONFIGURED SWITCH INTERFACES section, click on Leaf2 (because this is where our uplink to the LAN is connected) a. Click on the big green plus sign to configure switch interfaces. i. In the Interfaces text field, enter 1/16 (because this is where the uplink cable is attached). Note: refer to the target topology diagram, for more information i In the Interface Selector Name text field, provide a name for the Interface Selector. Note, since the Dell_Switch is connected to this interface, name the Interface Selector Dell_Switch_IFSel. From the Interface Policy Group pull down menu, select Create Interface Policy Group and the CREATE ACCESS PORT POLICY GROUP dialog is displayed. 1. Provide a name (e.g., Dell_Switch_PG) 2. From the Link Level Policy pull down menu, choose Create Link Level Policy and the CREATE LINK LEVEL POLICY dialog is displayed. a. Provide a name (e.g., 1G_Interface) b. Ensure Auto Negotiation is set to on c. Set the speed to 1 Gbps (since our uplink to the Dell switch is 1G) d. Click SUBMIT 3. Click SUBMIT b. Click SAVE 8

9 2. Click SAVE vi. v Click SUBMIT Next to each INTERFACE POLICY GROUP, under the SELECT INTERFACES column, select the All radio button. b. Click FINISH Create a VMM Domain 1. Under TENANTS -> mgmt, expand Tenant mgmt, expand networking and then right click Networking and select create Bridge Domain. a. Enter a name (e.g., VMM_BD) b. Click SUBMIT 2. Under VM NETWORKING -> POLICIES, right click VM Provider VMware and click Create vcenter Domain. 3. In the CREATE VCENTER DOMAIN dialog: a. Enter a name (i.e., vcenter1) b. Ensure that the VMWare vsphere Distributed Switch radio button is selected. c. From the Associated Attachable Entity Profile pull down menu, select Create Attachable Entity Profile i. Provide a name (i.e., vcenteraep) Click NEXT and the ASSOCIATION TO INTERFACES dialog is displayed 1. Click the + under Select the interfaces and the CONFIGURE INTERFACE, PC, AND VPC dialog is displayed. a. In the CONFIGURED SWITCH INTERFACES section, click on Leaf1 i. Click on the big green plus sign to configure switch interfaces. 1. In the Interfaces text field, since this is Leaf1, enter 1/3-5. Note, refer to the target topology diagram, these are the interfaces connected to the VSAN_Cluster. 2. In the Interface Selector Name text field, provide a name for the Interface Selector. Note, since the VSAN_Cluster is attached to these three ports, I m going to name the Interface Selector VSAN_Cluster_IFSel. 3. From the Interface Policy Group pull down menu, select Create Interface Policy Group and the CREATE ACCESS PORT POLICY GROUP dialog is displayed. a. Provide a name (e.g., VSAN_Cluster_PG) b. Click SUBMIT Click SAVE b. In the CONFIGURED SWITCH INTERFACES section, click on Leaf2 i. Click on the big green plus sign to configure switch interfaces. 1. In the Interfaces text field, since this is Leaf1, enter 1/3-4. Note, refer to the target topology diagram, these are the interfaces connected to the TwoNode_Cluster. 2. In the Interface Selector Name text field, provide a name for the Interface Selector. Note, since the TwoNode_Cluster is attached to these three ports, I m going to name the Interface Selector TwoNode_Cluster_IFSel. 9

10 3. From the Interface Policy Group pull down menu, select Create Interface Policy Group and the CREATE ACCESS PORT POLICY GROUP dialog is displayed. a. Provide a name (e.g., TwoNode_Cluster_PG) b. Click SUBMIT Click SAVE c. Click SAVE 2. Click SUBMIT 3. Next to each INTERFACE POLICY GROUP, under the SELECT INTERFACES column, select the All radio button. 4. Click FINISH d. From the VLAN Pool pull down, select create VLAN Pool i. Provide a name (i.e., vcentervlanpool) i Select the Dynamic Allocation radio button Click the + next to encap blocks 1. Provide the starting VLAN ID (i.e., 100) 2. Provide the ending VLAN ID (i.e., 300) 3. Click OK iv. Click SUBMIT e. Click the + sign next to vcenter Credentials and the CREATE VCENTER CREDENTIAL dialog is displayed. i. Provide a name (i.e., admin) i iv. Provide a username of an actual user (e.g., root) that has been configured to have administrator rights on the vcenter instance you ll be connecting to. Provide the password for the user specified above (e.g., Dangerous ). Enter the password again v. Click OK. f. Click the + sign next to vcenter/vsheild i. Provide a name (e.g., vcenter1) Provide the IP Address of the vcenter (e.g., ) i iv. Ensure that VDS Version is set to vcenter Default Enter the name of the Datacenter in vcenter that you ll want to configure (e.g., Demo) v. From the Management EPG, select Create Management EPG 1. In the Application Profile, select Create Application Profile Under Tenant mgmt and the CREATE APPLICATION PROFILE dialog is displayed. a. Provide a name (e.g., VMM_APP_Profile) b. Click SUBMIT 2. Provide a name (e.g., VMM_EPG) 3. From the Bridge Domain pull down menu, select VMM_BD 4. Click Submit vi. v From the Associated Credential pull down, select admin which was created earlier. Click OK g. Click Submit Verify APIC to vcenter connectivity 10

11 1. Under VM NETWORKING -> INVENTORY, expand VMware, then select the VMM Domain that you just added (i.e., vcenter1). In the PROPERTIES window to the right, you should see your vcenter instance and it should have a state of Online. a. Note, you can also expand the vcenter instance and then expand Hypervisors to see the Hypervisors that are being managed by Verify vcenter to APIC connectivity After you have added the vcenter credentials to APIC and clicked submit, APIC will automatically create a VMware vsphere Distributed Switch that can be viewed in vcenter under Home -> Networking. Note the name of the VDS is the same as the name of the VMM Domain that I created in APIC CONFIGURE THE DISTRIBUTED VSWITCH IN VCENTER Before you can use the VDS created by APIC, you ll need to perform a few configuration steps in vcenter. 1. Click on the vcenter1 Distributed Switch under the vcenter-vsncs-test folder. 2. Select the summary tab and then click on Add Host and the Select Hosts and Physical Adapters dialog is shown. 3. Select the interfaces that are attached to the ACI leaf interfaces. Based on the Physical Topology provided above, this would be vmnic1 on the ESX Servers in the VSAN_Cluster and vmnic5 on the ESX Servers in the TwoNode_Cluster. 4. Click next, next, next and finish. 5. To view the changes, select Home, Inventory, Hosts and Clusters and then select one of the hosts 6. For each host, under the configuration tab, select Networking, vsphere Distributed Switch and you should see a Distributed vswitch named vcenter1. 7. Notice that this newly created VDS does not have any Port Groups associated with it. When using APIC, the creation of VDS Port Groups are controlled by APIC through the use of End Point Groups (EPGs). Basically there is a one-to-one relationship between a VDS Port Group (visible in vcenter) and an ACI End Point Group (visible in APIC). CREATE THE RP4VM NETWORKS VIA APIC Before we begin the RecoverPoint for Virtual Machines (RP4VM) installation process, we ll need to create the Networks that RP4VM requires. As shown in the Logical Topology diagram (above), we ll need to create 4 Networks per site. These networks are: Site A iscsi1 Site A iscsi2 Site A - LAN Site A WAN Site B iscsi1 Site B iscsi2 Site B - LAN Site B WAN NOTE: We are using two different WAN networks to simulate the RP4VM instances are located in different data centers. That having been said, you would also typically have different vcenter and APIC instances when you are configuring this in the real world. 11

12 Each of the network instances above will be associated with an EPG created in APIC as follows. Create VMM EPGs The EPGs created in this section will be associated with the VMM Domain and will be visible in vcenter. In order to get the LAN traffic to use the uplink on Leaf2 port 1/16, another EPG will need to be created and associated with a different Domain. Those steps will be covered in the next section Create Uplink EPG. 1. From APIC, Click TENANTS and then ADD TENANT 2. In the CREATE TENANT dialog: a. provide a name (i.e., RP4VM) b. Select a Security Domain (i.e., all) NOTE: You would probably want to something a bit more intelligent here if this was a real world example. c. Click NEXT d. Click the large plus sign to add a network and the CREATE NEW NETWORK dialog is displayed. i. Provide a name (i.e., RP4VM_NET) i Ensure that Create A Bridge Domain check box is selected Click NEXT and the Specify Bridge Domain for the Network is displayed 1. Provide a name (i.e., RP4VM_BD) 2. Click OK iv. Click FINISH 3. Ensure that the tenant RP4VM is selected and expand Tenant RP4VM 4. Select Networking -> Bridge Domains -> RP4VM_BD a. Set L2 Unknown Unicast to Flood. Note: This is only necessary due to a limitation with APIC and its inability to learn vmknic MAC Addresses. b. Click Submit 5. Under Tenant RP4VM, right click Application Profiles and select CREATE APPLICATION PROFILE. The CREATE APPLICATION PROFILE Dialog is displayed. a. Provide a name (i.e., RP4VM_AP) b. Click the + under EPGs and the CREATE APPLICATION EPG dialog is displayed i. Provide a name (i.e., SiteA_iSCSI1) i iv. In the Bridge Domain pull down select RP4VM_BD Click the + sign next to Associated Domain Profiles (VMs or bare metals) From the Domain Profile pull down select vcenter1 and ensure that both Deployment Immediacy amd Resolution Immediacy are set to Immediate. v. Click update vi. Click OK c. Repeat step b (above) for each network required to support RP4VM (should be a total of 8 in this example). When complete, the CREATE APPLICATION PROFILE dialog will look something like the following. 12

13 d. Select SiteA-WAN by single clicking on it under EPGs e. Click the + under Provided Contracts and the ADD PROVIDED CONTRACT dialog is displayed i. Under Name, select common/default Click OK f. Click the + under Consumed Contracts and the ADD CONSUMED CONTRACT dialog is displayed i. Under Name, select common/default Click OK g. Repeat steps e and f for SiteB-WAN Note: In order for communication to be possible between two EPGs, a contract must be used. The default contract used above allows all traffic to be passed to and from the WAN EPGs. If this were an actual deployment, you would probably want to limit the traffic that would be allowed to pass between the two WAN EPGs. This can be done by creating a new contract. h. Click submit If you go back to vcenter, you ll notice that there are now 8 new port group associated with the vcenter1 VDS. See below for an example of what this would look like. 13

14 CREATE UPLINK EPG The following steps will create and configure the EPG that will be used to allow the VMM LAN EPGs to use the uplink port on leaf 2 interface 1/ Under Tenant RP4VM > Application Profiles > RP4VM_AP, right click Application EPGs and select Create Application EPG a. Provide a name (i.e., LAN_Uplink) b. Click the + under EPGs and the CREATE APPLICATION EPG dialog is displayed i. Provide a name (i.e., SiteA_iSCSI1) i iv. In the Bridge Domain pull down select RP4VM_BD Click the + sign next to Associated Domain Profiles (VMs or bare metals) From the Domain Profile pull down select Dell_Switch_Port16 and ensure that both Deployment Immediacy amd Resolution Immediacy are set to Immediate. v. Click update vi. Click FINISH 2. Under Tenant RP4VM > Application Profiles > RP4VM_AP > Application EPGs, expand EPG LAN_Uplink a. Click Contracts i. From the ACTIONS pull down menu, select Add Provided Contract and the ADD PROVIDED CONTRACT dialog is displayed: 1. Under Name, select common/default 14

15 2. Click OK From the ACTIONS pull down menu, select Add Consumed Contract and the ADD CONSUMED CONTRACT dialog is displayed: 1. Under Name, select common/default 2. Click OK b. Right click Static Bindings (Paths) and select Deploy Static EPG on PC, VPC, or Interface and the DEPLOY STATIC EPG ON PC, VPC, OR INTERFACE dialog is displayed. i. Ensure the Path Type is set to Port From the Path pull down menu, select leaf2 > Interface 1/16 i iv. In the Encap text area, type vlan-99 Select a Deployment Immediacy of Immediate v. Set the Mode to Untagged. Note: I am choosing Untagged because I am connected to a LAN segment that uses untagged frames, you re configuration may be different. vi. Click SUBMIT 3. Under Tenant RP4VM > Application Profiles > RP4VM_AP > Application EPGs, expand EPG SiteA_LAN a. Click Contracts i. From the ACTIONS pull down menu, select Add Provided Contract and the ADD PROVIDED CONTRACT dialog is displayed: 1. Under Name, select common/default 2. Click OK From the ACTIONS pull down menu, select Add Consumed Contract and the ADD CONSUMED CONTRACT dialog is displayed: 1. Under Name, select common/default 2. Click OK 4. Under Tenant RP4VM > Application Profiles > RP4VM_AP > Application EPGs, expand EPG SiteB_LAN a. Click Contracts i. From the ACTIONS pull down menu, select Add Provided Contract and the ADD PROVIDED CONTRACT dialog is displayed: 1. Under Name, select common/default 2. Click OK From the ACTIONS pull down menu, select Add Consumed Contract and the ADD CONSUMED CONTRACT dialog is displayed: 1. Under Name, select common/default 2. Click OK NOTE: For some reason after following the above, the Policy Group 1G_Switch was associated with the wrong AEP. It should have been ExternalNetwork but was instead VMMDomain. MODIFY ISCSI PORT GROUPS TO ALLOW ISCSI As explained in the Logical topology details section (above), this case study uses the ESXi Software based iscsi initiator. This iscsi Initiator will be used by the RP4VM splitter to communicate with the RP4VM appliance that is running on the ESX Servers (refer to the Logical Topology diagram for more information). In order for this communication to take place, we need to bind the iscsi Initiator to vmknics that can be attached to the appropriate iscsi Port Groups. The problem is the iscsi Initiator can only be bound to vmknics that are attached to Port Groups that have a compliant teaming and failover policy and Port Groups created via APIC do not compliant. To resolve this issue, perform the following steps: 1. In vcenter, navigate to Home -> Networking 15

16 2. Under the vcenter1 VDS, right click one of the iscsi Port Groups (e.g., SiteA_iSCSI1) and choose Edit Settings 3. Click on Teaming and Failover and note that there are 8 Active uplinks. 4. Move uplink2 uplink 8 to Unused Uplinks by selecting them and then clicking Move Down until they are under Unused Uplinks. 5. Click OK 6. Repeat for every iscsi port group CONFIGURE VMKNICS AND ATTACH TO ISCSI PORT GROUPS In this step we will create two vmknics on every ESX Server and associate them with the appropriate iscsi Port Group. The IP Addresses defined in the IP Address assignment table (above) and provided below for ease of reference will be used. NOTE: This white paper describes a configuration that uses a separate network (Broadcast Domain) for each of the iscsi Networks. This is being done for example purposes only and is not a requirement for RP4VM. Refer to the RP4VM Installation and Deployment guide for further information. 1. Create vmknics a. In vcenter, navigate to Home -> Hosts and Clusters and then select the server with an IP Address of (a.k.a Site A ESX-1). b. Under the Configuration tab, click Networking and then vsphere Distributed Switch. c. Click Manage Virtual Adapters next to Distributed Switch: vcenter1 and the Manage Virtual Adapters dialog is displayed. d. Click Add e. Select New virtual adapter and click Next and click Next again, this will bring you to the Connection Settings dialog. f. Ensure the Select port group radio button is selected and then select the port group created in APIC that is associated with the vmkernel NIC you are creating. In this case it would be the port group SiteA_iSCSI1. g. Click Next. h. Enter the IP Address in this case and the Subnet Mask of i. Click Next and then click Finish. j. Repeat the above steps for all vmknics required. In this case study there are Bind iscsi SW initiator to the vmknics created above. a. In vcenter, navigate to Home -> Hosts and Clusters and then select the server with an IP Address of (a.k.a Site A ESX-1). b. Under the Configuration tab, click Storage Adapters. c. Select the iscsi Software Adapter and then click Properties. The iscsi Initiator Properties dialog is displayed. d. Click the Network Configuration tab and then click Add. e. Select one of the vmknics created above and then click OK. See below for an example. 16

17 f. Repeat steps d and e for the other vmkinc on this server g. Repeat the above for all ESX Servers in the environment 3. To verify that the APIC and ESX configurations are correct, use vmkping while in an ssh session with each ESX server to verify that connectivity can be established between the vmknics. INSTALL RP4VM Once the steps above have been completed, you can install RecoverPoint for Virtual Machines as described in the RecoverPoint for VMs 4.2 Installation and Deployment Guide_ _02.pdf. This white paper will not attempt to duplicate those instructions but will instead point out the place in the installation process where you ll see the results of the work you performed above. During Deploy OVF Template When you are deploying the RecoverPoint for Virtual Machines OVF Template, you ll be prompted to map the networks defined in the RP4VM Template to networks in your inventory (see screen shot below). You ll note that the pull down menu contains all of the EndPoint Groups you created in APIC and associated with the VMM Domain vcenter1. 17

18 18

19 CONTACT US To learn more about how EMC products, services, and solutions can help solve your business and IT challenges, contact your local representative or authorized reseller, visit or explore and compare products in the EMC Store. EMC 2, EMC, the EMC logo, EMC Connectrix are registered trademarks or trademarks of EMC Corporation in the United States and other countries. VMware is a registered trademark or trademark of VMware, Inc., in the United States and other jurisdictions. Copyright 2016 EMC Corporation. All rights reserved. Published in the USA. 01/16 Whitepaper H EMC believes the information in this document is accurate as of its publication date. The information is subject to change without notice.