SlideShare a Scribd company logo

Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding)

open-e, profile picture
open-e

The document provides a detailed, step-by-step guide for setting up active-active iSCSI failover using Open-E DSS v7 software. It outlines the necessary hardware and network configurations, the creation of volume groups, and the implementation of volume replication between two nodes. Additional instructions include testing failover functions and managing replication tasks to ensure effective failover operations.

Technology
1 of 52
Download to read offline
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
Step-by-Step Guide to Open-E DSS V7 Active-Active iSCSI Failover Software Version: DSS ver. 7.00 up10 Presentation updated: June 2013 www.open-e.com 1
Open-E DSS V7 Active-Active iSCSI Failover TO SET UP ACTIVE-ACTIVE ISCSI FAILOVER, PERFORM THE FOLLOWING STEPS: 1. Hardware configuration 2. Network Configuration: • Set server hostnames and Ethernet ports on both nodes (node-a, node-b) 3. Configure the node-b: • Create a Volume Group, iSCSI Volume • Configure Volume Replication mode (destination and source mode) – define remote mode of binding, create Volume Replication task and start the replication task 4. Configure the node-a: • Create a Volume Group, iSCSI Volume • Configure Volume Replication mode (source and destination mode), create Volume Replication task and start the replication task. 5. Create targets (node-a and node-b) 6. Configure Failover (node-a and node-b) 7. Start Failover Service 8. Test Failover Function 9. Run Failback Function www.open-e.com 2
Open-E DSS V7 Active-Active iSCSI Failover Storage client 1 1. Hardware Configuration Storage client 2 IP:192.168.0.101 eth0 IP:192.168.21.101 (MPIO 1) IP:192.168.22.101 (MPIO 2) IP:192.168.1.107 (Ping Node) eth1 eth1 IP:192.168.31.101 (MPIO 1) IP:192.168.32.101 (MPIO 2) eth2 eth2 IP:192.168.0.102 eth0 Data Server (DSS1) Switch 1 IP Address:192.168.0.220 RAID System 1 IP:192.168.0.220 Please use external tool to monitor failures in connections between switches. eth0 Storage Client Access, Multipath Auxiliary connection (Heartbeat) (eth1, eth2) Resources Pools and Virtual IP Addresses: Node-a 192.168.21.100; iSCSI Target 0 Node-b 192.168.22.100; iSCSI Target 1 Storage Client Access, Multipath Auxiliary connection (Heartbeat) IP:192.168.2.220 (eth3, eth4) Volume Replication, Auxilliary connection (Heartbeat) IP:192.168.5.220 Volume Groups (vg00) iSCSI volumes (lv0000, lv0001) iSCSI targets node-b Switch 2 IP Address:192.168.0.221 RAID System 2 Note: Port used for WEB GUI management bond1 (MPIO 1) IP:192.168.31.102 (MPIO 2) IP:192.168.32.102 (Ping Node) IP:192.168.2.107 RSTP/Port Trunk IP:192.168.1.220 IP:192.168.21.102 IP:192.168.22.102 Data Server (DSS2) node-a bond0 (MPIO 1) (MPIO 2) eth5 Note: Resources Pools and Virtual IP Addresses: Node-a 192.168.31.100; iSCSI Target 0 Node-b 192.168.32.100; iSCSI Target 1 It is strongly recommended to use direct point-to-point and if possible 10GbE connection for the volume replication. Optionally Round-Robin-Bonding with 1GbE or 10GbE ports can be configured for the volume replication. The volume replication connection can work over the switch, but the most reliable is a direct connection. iSCSI Failover/Volume Replication (eth5) Port used for WEB GUI management eth0 IP:192.168.0.221 Storage Client Access, Multipath Auxiliary connection (Heartbeat) (eth1, eth2) IP:192.168.1.221 Storage Client Access, Multipath, Auxiliary connection (Heartbeat) (eth3, eth4) IP:192.168.2.221 bond1 Volume Replication , Auxilliary connection (Heartbeat) eth5 IP:192.168.5.221 Volume Groups (vg00) iSCSI volumes (lv0000, lv0001) iSCSI targets NOTE: To prevent switching loops, it's recommended to use RSTP (802.1w) or Port Trunking on network switches used to build A-A Failover network topology. www.open-e.com bond0 3
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 2. Network Configuration IP Address:192.168.0.221 After logging on to the Open-E DSS V7 (node-b), please go to SETUP and choose the "Network interfaces" option. In the Hostname box, replace the "dss" letters in front of the numbers with "node-b" server, in this example "node-b-59979144" and click the apply button (this will require a reboot). www.open-e.com 4
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 2. Network Configuration IP Address:192.168.0.221 Next, select eth0 interface and in the IP address field, change the IP address from 192.168.0.220 to 192.168.0.221 Then click apply (this will restart network configuration). www.open-e.com 5
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 2. Network Configuration IP Address:192.168.0.221 Once again, select Interfaces and in the "Create new bond interface" function check two boxes with eth1 and eth2. Next, in the field Create select a bonding mode. In this example select New balance-alb. Next, in the field Adress IP enter 192.168.1.221 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button. www.open-e.com 6
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 2. Network Configuration IP Address:192.168.0.221 Again, in the "Create new bond interface" function check two boxes with eth3 and eth4. Next, in the field Create select a bonding mode. In this example select New balance-alb. Next, in the Address IP field enter 192.168.2.221 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button. www.open-e.com 7
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 2. Network Configuration IP Address:192.168.0.221 Next, select eth5 interface and in the IP address field, change the IP address from 192.168.5.220 to 192.168.5.221 and click the apply button. www.open-e.com 8
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 2. Network Configuration IP Address:192.168.0.220 After logging in to node-a, please go to SETUP and choose the "Network interfaces" option. In the Hostname box, replace the "dss" letters in front of the numbers with "node-a" server, in this example "node-a-39166501"and click apply (this will require a reboot). www.open-e.com 9
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 2. Network Configuration IP Address:192.168.0.220 Next, select Interfaces and in the "Create new bond interface" function check two boxes with eth1 and eth2. Next, in the field Create select a bonding mode. In this example select New balance-alb. In the field Adress IP enter 192.168.1.220 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button. www.open-e.com 10
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 2. Network Configuration IP Address:192.168.0.220 Again in the "Create new bond interface" function check two boxes with eth3 and eth4. Next, in the field Create select a bonding mode. In this example select New balance-alb. Next, in the field Adress IP enter 192.168.2.220 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button. www.open-e.com 11
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 Under CONFIGURATION, select "Volume manager", then click on "Volume groups". In the Unit manager function menu, add the selected physical units (Unit MD0 or other) to create a new volume group (in this case, vg00) and click the apply button. www.open-e.com 12
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 Select the appropriate volume group (vg00) from the list on the left and create a new iSCSI volume of the required size. Please set 2 logical volumes in the Active-Active option. The 1st logical volume (lv0000) will be a destination of the replication process on node-b. Next, check the box Use volume replication. After assigning an appropriate amount of space for the iSCSI volume, click the apply button www.open-e.com 13
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 Next, create the 2nd logical volume on the node-b. Logical volume (lv0001) will be the source of the replication process on this node. Next, check the box Use volume replication. After assigning an appropriate amount of space for the iSCSI volume, click the apply button. www.open-e.com 14
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 2 logical iSCSI Volume Block I/O are now configured. iSCSI volume (lv0000) is set to destination iSCSI volume (lv0001) is set to source www.open-e.com 15
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 Under CONFIGURATION, select "Volume manager" and then click on "Volume groups". Add the selected physical units (Unit S001 or other) to create a new volume group (in this case, vg00) and click apply button. Volume Groups (vg00) www.open-e.com 16
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 Select the appropriate volume group (vg00) from the list on the left and create a new iSCSI volume of the required size. Please set 2 logical volumes in the Active-Active option. The 1st logical volume (lv0000) will be a source of the replication process on the node-a. Next, check the box for "Use volume replication" After assigning an appropriate amount of space to the iSCSI volume, click the apply button. NOTE: The source and destination volumes must be of identical size. www.open-e.com 17
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 Next, create the 2nd logical volume on the node-a. Logical volume (lv0001) will be a destination of the replication process on this node. Next, check the box for "Use volume replication". After assigning an appropriate amount of space to the iSCSI volume, click the apply button. NOTE: The source and destination volumes must be of identical size. www.open-e.com 18
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 2 logical iSCSI Volume Block I/O are now configured. iSCSI volume (lv0000) is set to source iSCSI volume (lv0001) is set to destination www.open-e.com 19
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 Now, on the node-b, go to "Volume replication". Within Volume replication mode function, check the Destination box for lv0000 and check the Source box for lv0001. Then, click the apply button. In the Hosts binding function, enter the IP address of node-a (in our example, this would be 192.168.5.220), enter node-a administrator password and click the apply button. NOTE: The remote node IP Address must be on the same subnet in order for the replication to communicate. VPN connections can work providing you are not using a NAT. Please follow example: • node-a: 192.168.5.220 • node-b: 192.168.5.221 www.open-e.com 20
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 Next, on the node-a, go to "Volume replication". Within Volume replication mode function, check the Source box for lv0000 and check the Destination box for lv0001. Next, click the apply button. www.open-e.com 21
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 In the Create new volume replication task, enter the task name in the Task name field, then click on the button. In the Destination volume field, select the appropriate volume (in this example, lv0000). In the Bandwidth for SyncSource (MB) field you must change the value. In the example, 35MB is used. Next, click the create button. NOTE: The "Bandwidth for SyncSource (MB)" need to be calculated based on available Ethernet Network throughput and number of replication tasks and the limitation factor (about 0.7). For example: 1 Gbit Ethernet and 2 replication tasks (assuming 1 Gbit provides about 100 MB/sec sustained network throughput) • Bandwidth for SyncSource (MB): = 0.7 * 100/ 2 = 35 For example: 10 Gbit Ethernet and 10 replication tasks (assuming 10 Gbit provides about 700 MB/sec sustained network throughput) • Bandwidth for SyncSource (MB): = 0.7 * 700/10 = 49 www.open-e.com 22
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 Now, in the Replication task manager function, click the corresponding "play" button to start the Replication task on the node-a. www.open-e.com 23
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 In the Replication tasks manager window, you may view information about currently running replication tasks. When a task is started, a date and time will appear. www.open-e.com 24
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 You can check the status of Volume Replication anytime in STATUS → "Tasks" → "Volume Replication" menu. Click on the button, located next to a task name (in this case Mirror_0000) to display detailed information on the current replication task. NOTE: Please allow the replication task to complete (similar to above with status being "Consistent") before writing to the iSCSI Logical Volume. www.open-e.com 25
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 Next, go to the node-b. Within Create new volume replication task, enter the task name in the Task name field, then click on the button. In the Destination volume field, select the appropriate volume (in this example, lv0001). As in the node-a, in the Bandwidth for SyncSource (MB) field you must change the value. In our example 35 MB is used. Next click the create button. www.open-e.com 26
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 In the Replication tasks manager function, click the corresponding "play" button to start the Replication task on the node-b: Mirror_0001. In this box you can find information about currently running replication tasks. When a task is started a date and time will appear. www.open-e.com 27
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 5. Create new target on the node-b IP Address:192.168.0.221 Choose CONFIGURATION, "iSCSI target manager" and "Targets" from the top menu. In the Create new target function, uncheck the box Target Default Name. In the Name field, enter a name for the new target and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 28
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 5. Create new target on the node-b IP Address:192.168.0.221 Next, you must set the 2nd target. Within the Create new target function, uncheck the box Target Default Name. In the Name field, enter a name for the 2nd new target and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 29
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 5. Create new target on the node-b IP Address:192.168.0.221 After that, select target0 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-0 → lv0000) and click attach button located under Action. NOTE: Volumes on both sides must have the same SCSI ID and LUN# for example: lv0000 SCSI ID on node-a = lv0000 SCSI ID on node-b. In this case before clickling the attach button please copy the SCSI and LUN# from this node. www.open-e.com 30
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 5. Create new target on the node-b IP Address:192.168.0.221 Next, select target1 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-1 → lv0001) and click attach button located under Action. NOTE: Both systems must have the same SCSI ID and LUN# www.open-e.com 31
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 5. Create new target on the node-a IP Address:192.168.0.220 On the node-a, choose CONFIGURATION, "iSCSI target manager" and "Targets" from the top menu. Within the Create new target function, uncheck the box Target Default Name. In the Name field, enter a name for the new target and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 32
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 5. Create new target on the node-a IP Address:192.168.0.220 Next, you must set the 2nd target. In the Create new target function, uncheck the box Target Default Name. In the Name field, enter a name for the 2nd new target and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 33
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 5. Create new target on the node-a IP Address:192.168.0.220 Select the target0 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-0 → lv0000) and click attach button located under Action. NOTE: Before clicking the attach button again, please paste the SCSI ID and LUN# (previously copied) from the node-b. www.open-e.com 34
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 5. Create new target on the node-a IP Address:192.168.0.220 Select the target1 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-1 → lv0001) and click attach button located under Action. NOTE: Before clicking the attach button again, please copy & paste the SCSI ID and LUN# from the node-b. www.open-e.com 35
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 On the node-a, go to SETUP and select "Failover". In the Auxiliary paths function, select the 1st New auxiliary path on the local and remote node and click the add new auxiliary path button. www.open-e.com 36
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 In the Auxiliary paths function, select the 2nd New auxiliary path on the local and remote node and click the add new auxiliary path button. www.open-e.com 37
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 In the Ping nodes function, enter two ping nodes. In the IP address field enter IP address and click the add new ping node button (according to the configuration in the third slide). In this example, IP address of the first ping node is: 192.168.1.107 and the second ping node: 192.168.2.107 www.open-e.com 38
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Next, go to the Resources Pool Manager function (on node-a resources) and click the add virtual IP button. After that, enter Virtual IP, (in this example 192.168.21.100 according to the configuration in the third slide) and select two appropriate interfaces on local and remote nodes. Then, click the add button. www.open-e.com 39
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Now, still on node-a resources (local node) enter the next Virtual IP address. Click add virtual IP enter Virtual IP, (in this example 192.168.31.100), and select two appropriate interfaces on the local and remote nodes. Then, click the add button. www.open-e.com 40
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Then, go to node-b resources and click the add virtual IP button again and enter the Virtual IP (In this example 192.168.22.100 according to the configuration in the third slide) and select two appropriate interfaces on the local and remote nodes. Then, click the add button. www.open-e.com 41
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Now, still on node-b resources, click the add virtual IP button and enter the next Virtual IP, (in this example 192.168.32.100, according to the configuration in the third slide) and select two appropriate interfaces on the local and remote nodes. Then, click the add button. www.open-e.com 42
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Now you have 4 Virtual IP addresses configured on two interfaces. www.open-e.com 43
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 When you are finished with setting the virtual IP, go to the iSCSI resources tab on the local node resources and click the add or remove targets button. After moving the target mirror-0 from Available targets to Targets already in cluster, click the apply button. www.open-e.com 44
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Next, go to the iSCSI resources tab on the remote node resources and click the add or remove targets button. After moving the target mirror-1 from Available targets to Targets already in cluster , click the apply button. www.open-e.com 45
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 After that, scroll to the top of the Failover manager function. At this point, both nodes are ready to start the Failover. In order to run the Failover service, click the start button and confirm this action by clicking the start button again. NOTE: If the start button is grayed out, the setup has not been completed. www.open-e.com 46
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 7. Start Failover Service IP Address:192.168.0.220 After clicking the start button, configuration of both nodes is complete. NOTE: You can now connect with iSCSI Initiators. The first storage client, in order to connect to target0 please setup multipath with following IP on the initiator side: 192.168.21.101 and 192.168.31.101. In order to connect to target1 please setup multipath with following IP on the initiator side: 192.168.22.101 and 192.168.32.101. For the next storage client please setup multipath accordingly: for access to target0: 192.168.21.102, 192.168.31.102 and for access to target1: 192.168.22.102, 192.168.32.102. www.open-e.com 47
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 8. Test Failover Function IP Address:192.168.0.220 In order to test Failover, go to the Resources pool manager function. Then, in the local node resources, click on the move to remote node button and confirm this action by clicking the move button. www.open-e.com 48
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 8. Test Failover Function IP Address:192.168.0.220 After performing this step, the status for local node resources should state "active on node-b (remote node)" and the Synchronization status should state "synced". www.open-e.com 49
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 9. Run Failback Function IP Address:192.168.0.220 In order to test failback, click the move to local node button in the Resources pool manager box for local node resources and confirm this action by clicking the move button. www.open-e.com 50
Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 9. Run Failback Function IP Address:192.168.0.220 After completing this step, the status for node-a resources should state "active on node-a (local node)" and the Synchronization status should state "synced". Then, you can apply the same actions for node-b resources. NOTE: The Active-Active option allows configuring resource pools on both nodes and makes it possible to run some active volumes on node-a and other active volumes on node-b. The Active-Active option is enabled with the TRIAL mode for 60 days or when purchasing the Active-Active Failover Feature Pack. The ActivePassive option allows configuring a resource pool only on one of the nodes. In such a case, all volumes are active on a single node only. The configuration and testing of Active-Active iSCSI Failover is now complete. www.open-e.com 51
Thank you! Follow Open-E: www.open-e.com 52

More Related Content

PDF
Open-E DSS V7 Remote Snapshot Control with CLI/API
open-e
 
PDF
Open-E DSS V7 Asynchronous Data Replication within a System
open-e
 
PDF
Open-E DSS V7 Asynchronous Data Replication over a WAN
open-e
 
PDF
Open-E DSS V7 Synchronous Volume Replication over a LAN
open-e
 
PDF
Open-E DSS V7 Asynchronous Data Replication over a LAN
open-e
 
PDF
Open-E DSS V7 Active-Passive iSCSI Failover
open-e
 
PDF
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
open-e
 
PDF
Open-E DSS V7 Active-Active iSCSI Failover on Intel Server Systems
open-e
 
Open-E DSS V7 Remote Snapshot Control with CLI/API
open-e
 
Open-E DSS V7 Asynchronous Data Replication within a System
open-e
 
Open-E DSS V7 Asynchronous Data Replication over a WAN
open-e
 
Open-E DSS V7 Synchronous Volume Replication over a LAN
open-e
 
Open-E DSS V7 Asynchronous Data Replication over a LAN
open-e
 
Open-E DSS V7 Active-Passive iSCSI Failover
open-e
 
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
open-e
 
Open-E DSS V7 Active-Active iSCSI Failover on Intel Server Systems
open-e
 

What's hot (20)

PDF
Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
open-e
 
PDF
Install oracle11gr2 rhel5
Edouard Anderson
 
PDF
9i hp relnotes
Anil Pandey
 
PDF
11g r2 rac_guide
guest66f94a7
 
PPT
Oracle Golden Gate
Muhammad Qasim
 
DOC
Schema replication using oracle golden gate 12c
uzzal basak
 
DOCX
Asm disk group migration from
Anar Godjaev
 
PDF
Oracle goldengate 11g schema replication from standby database
uzzal basak
 
PDF
Colvin RMAN New Features
Enkitec
 
PPTX
Hadoop Cluster - Basic OS Setup Insights
Sruthi Kumar Annamnidu
 
PPT
Oracle 10g Performance: chapter 00 sampling
Kyle Hailey
 
PDF
Rac on NFS
mengjiagou
 
PPT
Open-E Backup to Attached Tape Drive
open-e
 
PDF
Perl Programming - 04 Programming Database
Danairat Thanabodithammachari
 
DOCX
C mode class
Accenture
 
DOC
gcis-zenworks7.2
KARLY21
 
PDF
9i lin relnotes
Anil Pandey
 
PPTX
Hive data migration (export/import)
Bopyo Hong
 
PDF
Beginbackup
oracle documents
 
PDF
12c installation
Osama Mustafa
 
Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
open-e
 
Install oracle11gr2 rhel5
Edouard Anderson
 
9i hp relnotes
Anil Pandey
 
11g r2 rac_guide
guest66f94a7
 
Oracle Golden Gate
Muhammad Qasim
 
Schema replication using oracle golden gate 12c
uzzal basak
 
Asm disk group migration from
Anar Godjaev
 
Oracle goldengate 11g schema replication from standby database
uzzal basak
 
Colvin RMAN New Features
Enkitec
 
Hadoop Cluster - Basic OS Setup Insights
Sruthi Kumar Annamnidu
 
Oracle 10g Performance: chapter 00 sampling
Kyle Hailey
 
Rac on NFS
mengjiagou
 
Open-E Backup to Attached Tape Drive
open-e
 
Perl Programming - 04 Programming Database
Danairat Thanabodithammachari
 
C mode class
Accenture
 
gcis-zenworks7.2
KARLY21
 
9i lin relnotes
Anil Pandey
 
Hive data migration (export/import)
Bopyo Hong
 
Beginbackup
oracle documents
 
12c installation
Osama Mustafa
 
Ad

Viewers also liked (20)

PDF
Pycon 2008: Python Command-line Tools *Nix
Lecturer UC Davis & Northwestern
 
PPTX
Red Hat Storage Day Seattle: Why Software-Defined Storage Matters
Red_Hat_Storage
 
PPT
Swift Architecture and Practice, by Alex Yang
Hui Cheng
 
PDF
Building RESTful APIs
Silota Inc.
 
PPTX
Software Defined presentation
John Rhodes
 
PDF
Microservices with Swagger, Flask and Docker
Dhilipsiva DS
 
PPTX
Core Concept: Software Defined Everything
Thanakrit Lersmethasakul
 
PPTX
"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011
Stephen Foskett
 
PDF
Mirantis OpenStack-DC-Meetup 17 Sept 2014
Mirantis
 
PPTX
REST Coder: Auto Generating Client Stubs and Documentation for REST APIs
Hiranya Jayathilaka
 
PDF
Rest in flask
Yehor Nazarkin
 
PDF
Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...
Innovecs
 
PPTX
SDN Abstractions
martin_casado
 
PDF
Rest API using Flask & SqlAlchemy
Alessandro Cucci
 
KEY
Nginx in production
Graham Weldon
 
PDF
Open stack architecture overview-meetup-6-6_2013
Mirantis
 
PDF
OpenStack keystone identity service
openstackindia
 
PDF
Software-Defined Storage (SDS)
Ali Mirfallah
 
PDF
Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...
LF Events
 
PDF
Anatomy of neutron from the eagle eyes of troubelshoorters
Sadique Puthen
 
Pycon 2008: Python Command-line Tools *Nix
Lecturer UC Davis & Northwestern
 
Red Hat Storage Day Seattle: Why Software-Defined Storage Matters
Red_Hat_Storage
 
Swift Architecture and Practice, by Alex Yang
Hui Cheng
 
Building RESTful APIs
Silota Inc.
 
Software Defined presentation
John Rhodes
 
Microservices with Swagger, Flask and Docker
Dhilipsiva DS
 
Core Concept: Software Defined Everything
Thanakrit Lersmethasakul
 
"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011
Stephen Foskett
 
Mirantis OpenStack-DC-Meetup 17 Sept 2014
Mirantis
 
REST Coder: Auto Generating Client Stubs and Documentation for REST APIs
Hiranya Jayathilaka
 
Rest in flask
Yehor Nazarkin
 
Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...
Innovecs
 
SDN Abstractions
martin_casado
 
Rest API using Flask & SqlAlchemy
Alessandro Cucci
 
Nginx in production
Graham Weldon
 
Open stack architecture overview-meetup-6-6_2013
Mirantis
 
OpenStack keystone identity service
openstackindia
 
Software-Defined Storage (SDS)
Ali Mirfallah
 
Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...
LF Events
 
Anatomy of neutron from the eagle eyes of troubelshoorters
Sadique Puthen
 
Ad

Similar to Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding) (20)

PDF
Open-E DSS V6 MPIO with ESXi 4.x
open-e
 
PDF
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
open-e
 
PDF
Open-E Backup to iSCSI Target Volume over a LAN
open-e
 
PDF
Automating auto-scaled load balancer based on linux and vm orchestrator
Andrew Yongjoon Kong
 
PDF
Vpn
Jose Rivera
 
PPTX
Network Automation Tools
Edwin Beekman
 
PDF
Linux router
Miguel E Arellano Quezada
 
PPT
Nat 03
Davinder Chauhan
 
PDF
Network topology by essay corp uk
Johnsmith5188
 
PDF
Palo Alto BGP configuration basics document
ramana899986
 
PDF
Ibm i series_lpar_migration_from_vscsi_to_npiv_within_or_different_frames
Gobinath Panchavarnam
 
PDF
Openstack installation using rdo multi node
Narasimha sreeram
 
DOCX
Implementation of cisco wireless lan controller (multiple wla ns)
IT Tech
 
PDF
Weave Your Microservices with Istio
All Things Open
 
PDF
All Things Open 2019 weave-services-istio
Lin Sun
 
PDF
Ato2019 weave-services-istio
Lin Sun
 
PDF
Mikro tik site to site eoip tunnel with i psec
Uttam Ds
 
DOCX
Linux Telephony
Ryan Ellingson
 
DOCX
Basic configuration access point (1)
Thomas Charles Mack (Leigh)
 
PPT
Sharing-Knowledge-OAM-3G-Ericsson .ppt
wafawafa52
 
Open-E DSS V6 MPIO with ESXi 4.x
open-e
 
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
open-e
 
Open-E Backup to iSCSI Target Volume over a LAN
open-e
 
Automating auto-scaled load balancer based on linux and vm orchestrator
Andrew Yongjoon Kong
 
Vpn
Jose Rivera
 
Network Automation Tools
Edwin Beekman
 
Linux router
Miguel E Arellano Quezada
 
Nat 03
Davinder Chauhan
 
Network topology by essay corp uk
Johnsmith5188
 
Palo Alto BGP configuration basics document
ramana899986
 
Ibm i series_lpar_migration_from_vscsi_to_npiv_within_or_different_frames
Gobinath Panchavarnam
 
Openstack installation using rdo multi node
Narasimha sreeram
 
Implementation of cisco wireless lan controller (multiple wla ns)
IT Tech
 
Weave Your Microservices with Istio
All Things Open
 
All Things Open 2019 weave-services-istio
Lin Sun
 
Ato2019 weave-services-istio
Lin Sun
 
Mikro tik site to site eoip tunnel with i psec
Uttam Ds
 
Linux Telephony
Ryan Ellingson
 
Basic configuration access point (1)
Thomas Charles Mack (Leigh)
 
Sharing-Knowledge-OAM-3G-Ericsson .ppt
wafawafa52
 

More from open-e (8)

PPT
Description of Open-E Snapshot
open-e
 
PPT
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...
open-e
 
PPT
Open-E DSS V6 How to Setup iSCSI Failover with XenServer
open-e
 
PPT
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...
open-e
 
PPT
Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...
open-e
 
PPT
Open-E DSS Synchronous Volume Replication over a WAN
open-e
 
PPT
Open-E Backup to Attached Tape Library
open-e
 
PDF
Backup of Data Residing on DSS V6 with Backup Exec
open-e
 
Description of Open-E Snapshot
open-e
 
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...
open-e
 
Open-E DSS V6 How to Setup iSCSI Failover with XenServer
open-e
 
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...
open-e
 
Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...
open-e
 
Open-E DSS Synchronous Volume Replication over a WAN
open-e
 
Open-E Backup to Attached Tape Library
open-e
 
Backup of Data Residing on DSS V6 with Backup Exec
open-e
 

Recently uploaded (20)

PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
Mark Billinghurst
 
PPTX
Tartificialntelligence_presentation.pptx
ry7r52mzb4
 
PDF
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
SOFTTECHHUB
 
PDF
Accuracy of neural networks in brain wave diagnosis of schizophrenia
IAESIJAI
 
PPTX
Spectroscopy.pptx food analysis technology
nawahassan45
 
PDF
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
Jian-Hong Pan
 
PDF
Diabetes mellitus diagnosis method based random forest with bat algorithm
IAESIJAI
 
PPTX
cloud_computing_Infrastucture_as_cloud_p
mainakbhattacharya20
 
PDF
Getting Started with Data Integration: FME Form 101
Safe Software
 
PDF
Network Security Unit 5.pdf for BCA BBA.
Serpent6
 
PPTX
OMC Textile Division Presentation 2021.pptx
JahangirAlam816069
 
PPTX
Machine Learning_overview_presentation.pptx
kondavamsidharreddy2
 
PDF
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
Peter Tan
 
PPTX
Programs and apps: productivity, graphics, security and other tools
4mqw9zch22
 
PDF
Heart disease approach using modified random forest and particle swarm optimi...
IAESIJAI
 
PDF
A comparative study of natural language inference in Swahili using monolingua...
IAESIJAI
 
PPTX
TechTalks-8-2019-Service-Management-ITIL-Refresh-ITIL-4-Framework-Supports-Ou...
bonakiduza1024
 
PDF
August Patch Tuesday
Ivanti
 
PDF
Video forgery: An extensive analysis of inter-and intra-frame manipulation al...
IAESIJAI
 
PPTX
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
muhammadmuneebnaeem7
 
Reach Out and Touch Someone: Haptics and Empathic Computing
Mark Billinghurst
 
Tartificialntelligence_presentation.pptx
ry7r52mzb4
 
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
SOFTTECHHUB
 
Accuracy of neural networks in brain wave diagnosis of schizophrenia
IAESIJAI
 
Spectroscopy.pptx food analysis technology
nawahassan45
 
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
Jian-Hong Pan
 
Diabetes mellitus diagnosis method based random forest with bat algorithm
IAESIJAI
 
cloud_computing_Infrastucture_as_cloud_p
mainakbhattacharya20
 
Getting Started with Data Integration: FME Form 101
Safe Software
 
Network Security Unit 5.pdf for BCA BBA.
Serpent6
 
OMC Textile Division Presentation 2021.pptx
JahangirAlam816069
 
Machine Learning_overview_presentation.pptx
kondavamsidharreddy2
 
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
Peter Tan
 
Programs and apps: productivity, graphics, security and other tools
4mqw9zch22
 
Heart disease approach using modified random forest and particle swarm optimi...
IAESIJAI
 
A comparative study of natural language inference in Swahili using monolingua...
IAESIJAI
 
TechTalks-8-2019-Service-Management-ITIL-Refresh-ITIL-4-Framework-Supports-Ou...
bonakiduza1024
 
August Patch Tuesday
Ivanti
 
Video forgery: An extensive analysis of inter-and intra-frame manipulation al...
IAESIJAI
 
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
muhammadmuneebnaeem7
 

Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding)

  • 1. Step-by-Step Guide to Open-E DSS V7 Active-Active iSCSI Failover Software Version: DSS ver. 7.00 up10 Presentation updated: June 2013 www.open-e.com 1
  • 2. Open-E DSS V7 Active-Active iSCSI Failover TO SET UP ACTIVE-ACTIVE ISCSI FAILOVER, PERFORM THE FOLLOWING STEPS: 1. Hardware configuration 2. Network Configuration: • Set server hostnames and Ethernet ports on both nodes (node-a, node-b) 3. Configure the node-b: • Create a Volume Group, iSCSI Volume • Configure Volume Replication mode (destination and source mode) – define remote mode of binding, create Volume Replication task and start the replication task 4. Configure the node-a: • Create a Volume Group, iSCSI Volume • Configure Volume Replication mode (source and destination mode), create Volume Replication task and start the replication task. 5. Create targets (node-a and node-b) 6. Configure Failover (node-a and node-b) 7. Start Failover Service 8. Test Failover Function 9. Run Failback Function www.open-e.com 2
  • 3. Open-E DSS V7 Active-Active iSCSI Failover Storage client 1 1. Hardware Configuration Storage client 2 IP:192.168.0.101 eth0 IP:192.168.21.101 (MPIO 1) IP:192.168.22.101 (MPIO 2) IP:192.168.1.107 (Ping Node) eth1 eth1 IP:192.168.31.101 (MPIO 1) IP:192.168.32.101 (MPIO 2) eth2 eth2 IP:192.168.0.102 eth0 Data Server (DSS1) Switch 1 IP Address:192.168.0.220 RAID System 1 IP:192.168.0.220 Please use external tool to monitor failures in connections between switches. eth0 Storage Client Access, Multipath Auxiliary connection (Heartbeat) (eth1, eth2) Resources Pools and Virtual IP Addresses: Node-a 192.168.21.100; iSCSI Target 0 Node-b 192.168.22.100; iSCSI Target 1 Storage Client Access, Multipath Auxiliary connection (Heartbeat) IP:192.168.2.220 (eth3, eth4) Volume Replication, Auxilliary connection (Heartbeat) IP:192.168.5.220 Volume Groups (vg00) iSCSI volumes (lv0000, lv0001) iSCSI targets node-b Switch 2 IP Address:192.168.0.221 RAID System 2 Note: Port used for WEB GUI management bond1 (MPIO 1) IP:192.168.31.102 (MPIO 2) IP:192.168.32.102 (Ping Node) IP:192.168.2.107 RSTP/Port Trunk IP:192.168.1.220 IP:192.168.21.102 IP:192.168.22.102 Data Server (DSS2) node-a bond0 (MPIO 1) (MPIO 2) eth5 Note: Resources Pools and Virtual IP Addresses: Node-a 192.168.31.100; iSCSI Target 0 Node-b 192.168.32.100; iSCSI Target 1 It is strongly recommended to use direct point-to-point and if possible 10GbE connection for the volume replication. Optionally Round-Robin-Bonding with 1GbE or 10GbE ports can be configured for the volume replication. The volume replication connection can work over the switch, but the most reliable is a direct connection. iSCSI Failover/Volume Replication (eth5) Port used for WEB GUI management eth0 IP:192.168.0.221 Storage Client Access, Multipath Auxiliary connection (Heartbeat) (eth1, eth2) IP:192.168.1.221 Storage Client Access, Multipath, Auxiliary connection (Heartbeat) (eth3, eth4) IP:192.168.2.221 bond1 Volume Replication , Auxilliary connection (Heartbeat) eth5 IP:192.168.5.221 Volume Groups (vg00) iSCSI volumes (lv0000, lv0001) iSCSI targets NOTE: To prevent switching loops, it's recommended to use RSTP (802.1w) or Port Trunking on network switches used to build A-A Failover network topology. www.open-e.com bond0 3
  • 4. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 2. Network Configuration IP Address:192.168.0.221 After logging on to the Open-E DSS V7 (node-b), please go to SETUP and choose the "Network interfaces" option. In the Hostname box, replace the "dss" letters in front of the numbers with "node-b" server, in this example "node-b-59979144" and click the apply button (this will require a reboot). www.open-e.com 4
  • 5. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 2. Network Configuration IP Address:192.168.0.221 Next, select eth0 interface and in the IP address field, change the IP address from 192.168.0.220 to 192.168.0.221 Then click apply (this will restart network configuration). www.open-e.com 5
  • 6. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 2. Network Configuration IP Address:192.168.0.221 Once again, select Interfaces and in the "Create new bond interface" function check two boxes with eth1 and eth2. Next, in the field Create select a bonding mode. In this example select New balance-alb. Next, in the field Adress IP enter 192.168.1.221 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button. www.open-e.com 6
  • 7. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 2. Network Configuration IP Address:192.168.0.221 Again, in the "Create new bond interface" function check two boxes with eth3 and eth4. Next, in the field Create select a bonding mode. In this example select New balance-alb. Next, in the Address IP field enter 192.168.2.221 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button. www.open-e.com 7
  • 8. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 2. Network Configuration IP Address:192.168.0.221 Next, select eth5 interface and in the IP address field, change the IP address from 192.168.5.220 to 192.168.5.221 and click the apply button. www.open-e.com 8
  • 9. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 2. Network Configuration IP Address:192.168.0.220 After logging in to node-a, please go to SETUP and choose the "Network interfaces" option. In the Hostname box, replace the "dss" letters in front of the numbers with "node-a" server, in this example "node-a-39166501"and click apply (this will require a reboot). www.open-e.com 9
  • 10. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 2. Network Configuration IP Address:192.168.0.220 Next, select Interfaces and in the "Create new bond interface" function check two boxes with eth1 and eth2. Next, in the field Create select a bonding mode. In this example select New balance-alb. In the field Adress IP enter 192.168.1.220 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button. www.open-e.com 10
  • 11. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 2. Network Configuration IP Address:192.168.0.220 Again in the "Create new bond interface" function check two boxes with eth3 and eth4. Next, in the field Create select a bonding mode. In this example select New balance-alb. Next, in the field Adress IP enter 192.168.2.220 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button. www.open-e.com 11
  • 12. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 Under CONFIGURATION, select "Volume manager", then click on "Volume groups". In the Unit manager function menu, add the selected physical units (Unit MD0 or other) to create a new volume group (in this case, vg00) and click the apply button. www.open-e.com 12
  • 13. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 Select the appropriate volume group (vg00) from the list on the left and create a new iSCSI volume of the required size. Please set 2 logical volumes in the Active-Active option. The 1st logical volume (lv0000) will be a destination of the replication process on node-b. Next, check the box Use volume replication. After assigning an appropriate amount of space for the iSCSI volume, click the apply button www.open-e.com 13
  • 14. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 Next, create the 2nd logical volume on the node-b. Logical volume (lv0001) will be the source of the replication process on this node. Next, check the box Use volume replication. After assigning an appropriate amount of space for the iSCSI volume, click the apply button. www.open-e.com 14
  • 15. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 2 logical iSCSI Volume Block I/O are now configured. iSCSI volume (lv0000) is set to destination iSCSI volume (lv0001) is set to source www.open-e.com 15
  • 16. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 Under CONFIGURATION, select "Volume manager" and then click on "Volume groups". Add the selected physical units (Unit S001 or other) to create a new volume group (in this case, vg00) and click apply button. Volume Groups (vg00) www.open-e.com 16
  • 17. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 Select the appropriate volume group (vg00) from the list on the left and create a new iSCSI volume of the required size. Please set 2 logical volumes in the Active-Active option. The 1st logical volume (lv0000) will be a source of the replication process on the node-a. Next, check the box for "Use volume replication" After assigning an appropriate amount of space to the iSCSI volume, click the apply button. NOTE: The source and destination volumes must be of identical size. www.open-e.com 17
  • 18. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 Next, create the 2nd logical volume on the node-a. Logical volume (lv0001) will be a destination of the replication process on this node. Next, check the box for "Use volume replication". After assigning an appropriate amount of space to the iSCSI volume, click the apply button. NOTE: The source and destination volumes must be of identical size. www.open-e.com 18
  • 19. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 2 logical iSCSI Volume Block I/O are now configured. iSCSI volume (lv0000) is set to source iSCSI volume (lv0001) is set to destination www.open-e.com 19
  • 20. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 Now, on the node-b, go to "Volume replication". Within Volume replication mode function, check the Destination box for lv0000 and check the Source box for lv0001. Then, click the apply button. In the Hosts binding function, enter the IP address of node-a (in our example, this would be 192.168.5.220), enter node-a administrator password and click the apply button. NOTE: The remote node IP Address must be on the same subnet in order for the replication to communicate. VPN connections can work providing you are not using a NAT. Please follow example: • node-a: 192.168.5.220 • node-b: 192.168.5.221 www.open-e.com 20
  • 21. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 Next, on the node-a, go to "Volume replication". Within Volume replication mode function, check the Source box for lv0000 and check the Destination box for lv0001. Next, click the apply button. www.open-e.com 21
  • 22. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 In the Create new volume replication task, enter the task name in the Task name field, then click on the button. In the Destination volume field, select the appropriate volume (in this example, lv0000). In the Bandwidth for SyncSource (MB) field you must change the value. In the example, 35MB is used. Next, click the create button. NOTE: The "Bandwidth for SyncSource (MB)" need to be calculated based on available Ethernet Network throughput and number of replication tasks and the limitation factor (about 0.7). For example: 1 Gbit Ethernet and 2 replication tasks (assuming 1 Gbit provides about 100 MB/sec sustained network throughput) • Bandwidth for SyncSource (MB): = 0.7 * 100/ 2 = 35 For example: 10 Gbit Ethernet and 10 replication tasks (assuming 10 Gbit provides about 700 MB/sec sustained network throughput) • Bandwidth for SyncSource (MB): = 0.7 * 700/10 = 49 www.open-e.com 22
  • 23. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 Now, in the Replication task manager function, click the corresponding "play" button to start the Replication task on the node-a. www.open-e.com 23
  • 24. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 In the Replication tasks manager window, you may view information about currently running replication tasks. When a task is started, a date and time will appear. www.open-e.com 24
  • 25. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 4. Configure the node-a IP Address:192.168.0.220 You can check the status of Volume Replication anytime in STATUS → "Tasks" → "Volume Replication" menu. Click on the button, located next to a task name (in this case Mirror_0000) to display detailed information on the current replication task. NOTE: Please allow the replication task to complete (similar to above with status being "Consistent") before writing to the iSCSI Logical Volume. www.open-e.com 25
  • 26. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 Next, go to the node-b. Within Create new volume replication task, enter the task name in the Task name field, then click on the button. In the Destination volume field, select the appropriate volume (in this example, lv0001). As in the node-a, in the Bandwidth for SyncSource (MB) field you must change the value. In our example 35 MB is used. Next click the create button. www.open-e.com 26
  • 27. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 3. Configure the node-b IP Address:192.168.0.221 In the Replication tasks manager function, click the corresponding "play" button to start the Replication task on the node-b: Mirror_0001. In this box you can find information about currently running replication tasks. When a task is started a date and time will appear. www.open-e.com 27
  • 28. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 5. Create new target on the node-b IP Address:192.168.0.221 Choose CONFIGURATION, "iSCSI target manager" and "Targets" from the top menu. In the Create new target function, uncheck the box Target Default Name. In the Name field, enter a name for the new target and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 28
  • 29. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 5. Create new target on the node-b IP Address:192.168.0.221 Next, you must set the 2nd target. Within the Create new target function, uncheck the box Target Default Name. In the Name field, enter a name for the 2nd new target and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 29
  • 30. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 5. Create new target on the node-b IP Address:192.168.0.221 After that, select target0 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-0 → lv0000) and click attach button located under Action. NOTE: Volumes on both sides must have the same SCSI ID and LUN# for example: lv0000 SCSI ID on node-a = lv0000 SCSI ID on node-b. In this case before clickling the attach button please copy the SCSI and LUN# from this node. www.open-e.com 30
  • 31. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS2) node-b 5. Create new target on the node-b IP Address:192.168.0.221 Next, select target1 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-1 → lv0001) and click attach button located under Action. NOTE: Both systems must have the same SCSI ID and LUN# www.open-e.com 31
  • 32. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 5. Create new target on the node-a IP Address:192.168.0.220 On the node-a, choose CONFIGURATION, "iSCSI target manager" and "Targets" from the top menu. Within the Create new target function, uncheck the box Target Default Name. In the Name field, enter a name for the new target and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 32
  • 33. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 5. Create new target on the node-a IP Address:192.168.0.220 Next, you must set the 2nd target. In the Create new target function, uncheck the box Target Default Name. In the Name field, enter a name for the 2nd new target and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 33
  • 34. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 5. Create new target on the node-a IP Address:192.168.0.220 Select the target0 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-0 → lv0000) and click attach button located under Action. NOTE: Before clicking the attach button again, please paste the SCSI ID and LUN# (previously copied) from the node-b. www.open-e.com 34
  • 35. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 5. Create new target on the node-a IP Address:192.168.0.220 Select the target1 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-1 → lv0001) and click attach button located under Action. NOTE: Before clicking the attach button again, please copy & paste the SCSI ID and LUN# from the node-b. www.open-e.com 35
  • 36. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 On the node-a, go to SETUP and select "Failover". In the Auxiliary paths function, select the 1st New auxiliary path on the local and remote node and click the add new auxiliary path button. www.open-e.com 36
  • 37. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 In the Auxiliary paths function, select the 2nd New auxiliary path on the local and remote node and click the add new auxiliary path button. www.open-e.com 37
  • 38. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 In the Ping nodes function, enter two ping nodes. In the IP address field enter IP address and click the add new ping node button (according to the configuration in the third slide). In this example, IP address of the first ping node is: 192.168.1.107 and the second ping node: 192.168.2.107 www.open-e.com 38
  • 39. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Next, go to the Resources Pool Manager function (on node-a resources) and click the add virtual IP button. After that, enter Virtual IP, (in this example 192.168.21.100 according to the configuration in the third slide) and select two appropriate interfaces on local and remote nodes. Then, click the add button. www.open-e.com 39
  • 40. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Now, still on node-a resources (local node) enter the next Virtual IP address. Click add virtual IP enter Virtual IP, (in this example 192.168.31.100), and select two appropriate interfaces on the local and remote nodes. Then, click the add button. www.open-e.com 40
  • 41. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Then, go to node-b resources and click the add virtual IP button again and enter the Virtual IP (In this example 192.168.22.100 according to the configuration in the third slide) and select two appropriate interfaces on the local and remote nodes. Then, click the add button. www.open-e.com 41
  • 42. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Now, still on node-b resources, click the add virtual IP button and enter the next Virtual IP, (in this example 192.168.32.100, according to the configuration in the third slide) and select two appropriate interfaces on the local and remote nodes. Then, click the add button. www.open-e.com 42
  • 43. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Now you have 4 Virtual IP addresses configured on two interfaces. www.open-e.com 43
  • 44. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 When you are finished with setting the virtual IP, go to the iSCSI resources tab on the local node resources and click the add or remove targets button. After moving the target mirror-0 from Available targets to Targets already in cluster, click the apply button. www.open-e.com 44
  • 45. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Next, go to the iSCSI resources tab on the remote node resources and click the add or remove targets button. After moving the target mirror-1 from Available targets to Targets already in cluster , click the apply button. www.open-e.com 45
  • 46. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 After that, scroll to the top of the Failover manager function. At this point, both nodes are ready to start the Failover. In order to run the Failover service, click the start button and confirm this action by clicking the start button again. NOTE: If the start button is grayed out, the setup has not been completed. www.open-e.com 46
  • 47. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 7. Start Failover Service IP Address:192.168.0.220 After clicking the start button, configuration of both nodes is complete. NOTE: You can now connect with iSCSI Initiators. The first storage client, in order to connect to target0 please setup multipath with following IP on the initiator side: 192.168.21.101 and 192.168.31.101. In order to connect to target1 please setup multipath with following IP on the initiator side: 192.168.22.101 and 192.168.32.101. For the next storage client please setup multipath accordingly: for access to target0: 192.168.21.102, 192.168.31.102 and for access to target1: 192.168.22.102, 192.168.32.102. www.open-e.com 47
  • 48. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 8. Test Failover Function IP Address:192.168.0.220 In order to test Failover, go to the Resources pool manager function. Then, in the local node resources, click on the move to remote node button and confirm this action by clicking the move button. www.open-e.com 48
  • 49. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 8. Test Failover Function IP Address:192.168.0.220 After performing this step, the status for local node resources should state "active on node-b (remote node)" and the Synchronization status should state "synced". www.open-e.com 49
  • 50. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 9. Run Failback Function IP Address:192.168.0.220 In order to test failback, click the move to local node button in the Resources pool manager box for local node resources and confirm this action by clicking the move button. www.open-e.com 50
  • 51. Open-E DSS V7 Active-Active iSCSI Failover Data Server (DSS1) node-a 9. Run Failback Function IP Address:192.168.0.220 After completing this step, the status for node-a resources should state "active on node-a (local node)" and the Synchronization status should state "synced". Then, you can apply the same actions for node-b resources. NOTE: The Active-Active option allows configuring resource pools on both nodes and makes it possible to run some active volumes on node-a and other active volumes on node-b. The Active-Active option is enabled with the TRIAL mode for 60 days or when purchasing the Active-Active Failover Feature Pack. The ActivePassive option allows configuring a resource pool only on one of the nodes. In such a case, all volumes are active on a single node only. The configuration and testing of Active-Active iSCSI Failover is now complete. www.open-e.com 51