SlideShare ist ein Scribd-Unternehmen logo
1 von 52
Downloaden Sie, um offline zu lesen
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

Weitere ähnliche Inhalte

Was ist angesagt?

Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server SystemsOpen-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systemsopen-e
 
Schema replication using oracle golden gate 12c
Schema replication using oracle golden gate 12cSchema replication using oracle golden gate 12c
Schema replication using oracle golden gate 12cuzzal basak
 
Asm disk group migration from
Asm disk group migration from Asm disk group migration from
Asm disk group migration from Anar Godjaev
 
Oracle goldengate 11g schema replication from standby database
Oracle goldengate 11g schema replication from standby databaseOracle goldengate 11g schema replication from standby database
Oracle goldengate 11g schema replication from standby databaseuzzal basak
 
Colvin RMAN New Features
Colvin RMAN New FeaturesColvin RMAN New Features
Colvin RMAN New FeaturesEnkitec
 
Hadoop Cluster - Basic OS Setup Insights
Hadoop Cluster - Basic OS Setup InsightsHadoop Cluster - Basic OS Setup Insights
Hadoop Cluster - Basic OS Setup InsightsSruthi Kumar Annamnidu
 
Oracle 10g Performance: chapter 00 sampling
Oracle 10g Performance: chapter 00 samplingOracle 10g Performance: chapter 00 sampling
Oracle 10g Performance: chapter 00 samplingKyle Hailey
 
Open-E Backup to Attached Tape Drive
Open-E Backup to Attached Tape DriveOpen-E Backup to Attached Tape Drive
Open-E Backup to Attached Tape Driveopen-e
 
C mode class
C mode classC mode class
C mode classAccenture
 
gcis-zenworks7.2
gcis-zenworks7.2gcis-zenworks7.2
gcis-zenworks7.2KARLY21
 
Hive data migration (export/import)
Hive data migration (export/import)Hive data migration (export/import)
Hive data migration (export/import)Bopyo Hong
 

Was ist angesagt? (20)

Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server SystemsOpen-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
 
Install oracle11gr2 rhel5
Install oracle11gr2 rhel5Install oracle11gr2 rhel5
Install oracle11gr2 rhel5
 
9i hp relnotes
9i hp relnotes9i hp relnotes
9i hp relnotes
 
11g r2 rac_guide
11g r2 rac_guide11g r2 rac_guide
11g r2 rac_guide
 
Oracle Golden Gate
Oracle Golden GateOracle Golden Gate
Oracle Golden Gate
 
Schema replication using oracle golden gate 12c
Schema replication using oracle golden gate 12cSchema replication using oracle golden gate 12c
Schema replication using oracle golden gate 12c
 
Asm disk group migration from
Asm disk group migration from Asm disk group migration from
Asm disk group migration from
 
Oracle goldengate 11g schema replication from standby database
Oracle goldengate 11g schema replication from standby databaseOracle goldengate 11g schema replication from standby database
Oracle goldengate 11g schema replication from standby database
 
Colvin RMAN New Features
Colvin RMAN New FeaturesColvin RMAN New Features
Colvin RMAN New Features
 
Hadoop Cluster - Basic OS Setup Insights
Hadoop Cluster - Basic OS Setup InsightsHadoop Cluster - Basic OS Setup Insights
Hadoop Cluster - Basic OS Setup Insights
 
Oracle 10g Performance: chapter 00 sampling
Oracle 10g Performance: chapter 00 samplingOracle 10g Performance: chapter 00 sampling
Oracle 10g Performance: chapter 00 sampling
 
Rac on NFS
Rac on NFSRac on NFS
Rac on NFS
 
Open-E Backup to Attached Tape Drive
Open-E Backup to Attached Tape DriveOpen-E Backup to Attached Tape Drive
Open-E Backup to Attached Tape Drive
 
Perl Programming - 04 Programming Database
Perl Programming - 04 Programming DatabasePerl Programming - 04 Programming Database
Perl Programming - 04 Programming Database
 
C mode class
C mode classC mode class
C mode class
 
gcis-zenworks7.2
gcis-zenworks7.2gcis-zenworks7.2
gcis-zenworks7.2
 
9i lin relnotes
9i lin relnotes9i lin relnotes
9i lin relnotes
 
Hive data migration (export/import)
Hive data migration (export/import)Hive data migration (export/import)
Hive data migration (export/import)
 
Beginbackup
BeginbackupBeginbackup
Beginbackup
 
12c installation
12c installation12c installation
12c installation
 

Andere mochten auch

Red Hat Storage Day Seattle: Why Software-Defined Storage Matters
Red Hat Storage Day Seattle: Why Software-Defined Storage MattersRed Hat Storage Day Seattle: Why Software-Defined Storage Matters
Red Hat Storage Day Seattle: Why Software-Defined Storage MattersRed_Hat_Storage
 
Swift Architecture and Practice, by Alex Yang
Swift Architecture and Practice, by Alex YangSwift Architecture and Practice, by Alex Yang
Swift Architecture and Practice, by Alex YangHui Cheng
 
Building RESTful APIs
Building RESTful APIsBuilding RESTful APIs
Building RESTful APIsSilota Inc.
 
Software Defined presentation
Software Defined presentationSoftware Defined presentation
Software Defined presentationJohn Rhodes
 
Microservices with Swagger, Flask and Docker
Microservices with Swagger, Flask and DockerMicroservices with Swagger, Flask and Docker
Microservices with Swagger, Flask and DockerDhilipsiva DS
 
"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011
"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011
"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011Stephen Foskett
 
Mirantis OpenStack-DC-Meetup 17 Sept 2014
Mirantis OpenStack-DC-Meetup 17 Sept 2014Mirantis OpenStack-DC-Meetup 17 Sept 2014
Mirantis OpenStack-DC-Meetup 17 Sept 2014Mirantis
 
REST Coder: Auto Generating Client Stubs and Documentation for REST APIs
REST Coder: Auto Generating Client Stubs and Documentation for REST APIsREST Coder: Auto Generating Client Stubs and Documentation for REST APIs
REST Coder: Auto Generating Client Stubs and Documentation for REST APIsHiranya Jayathilaka
 
Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...
Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...
Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...Innovecs
 
Rest API using Flask & SqlAlchemy
Rest API using Flask & SqlAlchemyRest API using Flask & SqlAlchemy
Rest API using Flask & SqlAlchemyAlessandro Cucci
 
Open stack architecture overview-meetup-6-6_2013
Open stack architecture overview-meetup-6-6_2013Open stack architecture overview-meetup-6-6_2013
Open stack architecture overview-meetup-6-6_2013Mirantis
 
OpenStack keystone identity service
OpenStack keystone identity serviceOpenStack keystone identity service
OpenStack keystone identity serviceopenstackindia
 
Software-Defined Storage (SDS)
Software-Defined Storage (SDS)Software-Defined Storage (SDS)
Software-Defined Storage (SDS)Ali Mirfallah
 
Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...
Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...
Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...LF Events
 
Anatomy of neutron from the eagle eyes of troubelshoorters
Anatomy of neutron from the eagle eyes of troubelshoortersAnatomy of neutron from the eagle eyes of troubelshoorters
Anatomy of neutron from the eagle eyes of troubelshoortersSadique Puthen
 

Andere mochten auch (20)

Pycon 2008: Python Command-line Tools *Nix
Pycon 2008:  Python Command-line Tools *NixPycon 2008:  Python Command-line Tools *Nix
Pycon 2008: Python Command-line Tools *Nix
 
Red Hat Storage Day Seattle: Why Software-Defined Storage Matters
Red Hat Storage Day Seattle: Why Software-Defined Storage MattersRed Hat Storage Day Seattle: Why Software-Defined Storage Matters
Red Hat Storage Day Seattle: Why Software-Defined Storage Matters
 
Swift Architecture and Practice, by Alex Yang
Swift Architecture and Practice, by Alex YangSwift Architecture and Practice, by Alex Yang
Swift Architecture and Practice, by Alex Yang
 
Building RESTful APIs
Building RESTful APIsBuilding RESTful APIs
Building RESTful APIs
 
Software Defined presentation
Software Defined presentationSoftware Defined presentation
Software Defined presentation
 
Microservices with Swagger, Flask and Docker
Microservices with Swagger, Flask and DockerMicroservices with Swagger, Flask and Docker
Microservices with Swagger, Flask and Docker
 
Core Concept: Software Defined Everything
Core Concept: Software Defined EverythingCore Concept: Software Defined Everything
Core Concept: Software Defined Everything
 
"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011
"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011
"FCoE vs. iSCSI - Making the Choice" from Interop Las Vegas 2011
 
Mirantis OpenStack-DC-Meetup 17 Sept 2014
Mirantis OpenStack-DC-Meetup 17 Sept 2014Mirantis OpenStack-DC-Meetup 17 Sept 2014
Mirantis OpenStack-DC-Meetup 17 Sept 2014
 
REST Coder: Auto Generating Client Stubs and Documentation for REST APIs
REST Coder: Auto Generating Client Stubs and Documentation for REST APIsREST Coder: Auto Generating Client Stubs and Documentation for REST APIs
REST Coder: Auto Generating Client Stubs and Documentation for REST APIs
 
Rest in flask
Rest in flaskRest in flask
Rest in flask
 
Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...
Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...
Reliable Python REST API (by Volodymyr Hotsyk) - Web Back-End Tech Hangout - ...
 
SDN Abstractions
SDN AbstractionsSDN Abstractions
SDN Abstractions
 
Rest API using Flask & SqlAlchemy
Rest API using Flask & SqlAlchemyRest API using Flask & SqlAlchemy
Rest API using Flask & SqlAlchemy
 
Nginx in production
Nginx in productionNginx in production
Nginx in production
 
Open stack architecture overview-meetup-6-6_2013
Open stack architecture overview-meetup-6-6_2013Open stack architecture overview-meetup-6-6_2013
Open stack architecture overview-meetup-6-6_2013
 
OpenStack keystone identity service
OpenStack keystone identity serviceOpenStack keystone identity service
OpenStack keystone identity service
 
Software-Defined Storage (SDS)
Software-Defined Storage (SDS)Software-Defined Storage (SDS)
Software-Defined Storage (SDS)
 
Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...
Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...
Learning From Real Practice of Providing Highly Available Hybrid Cloud Servic...
 
Anatomy of neutron from the eagle eyes of troubelshoorters
Anatomy of neutron from the eagle eyes of troubelshoortersAnatomy of neutron from the eagle eyes of troubelshoorters
Anatomy of neutron from the eagle eyes of troubelshoorters
 

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

Open-E DSS V6 MPIO with ESXi 4.x
Open-E DSS V6 MPIO with ESXi 4.xOpen-E DSS V6 MPIO with ESXi 4.x
Open-E DSS V6 MPIO with ESXi 4.xopen-e
 
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft WindowsHow to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windowsopen-e
 
Open-E Backup to iSCSI Target Volume over a LAN
Open-E Backup to iSCSI Target Volume over a LANOpen-E Backup to iSCSI Target Volume over a LAN
Open-E Backup to iSCSI Target Volume over a LANopen-e
 
Automating auto-scaled load balancer based on linux and vm orchestrator
Automating auto-scaled load balancer based on linux and vm orchestratorAutomating auto-scaled load balancer based on linux and vm orchestrator
Automating auto-scaled load balancer based on linux and vm orchestratorAndrew Yongjoon Kong
 
Network Automation Tools
Network Automation ToolsNetwork Automation Tools
Network Automation ToolsEdwin Beekman
 
Network topology by essay corp uk
Network topology by essay corp ukNetwork topology by essay corp uk
Network topology by essay corp ukJohnsmith5188
 
Ibm i series_lpar_migration_from_vscsi_to_npiv_within_or_different_frames
Ibm i series_lpar_migration_from_vscsi_to_npiv_within_or_different_framesIbm i series_lpar_migration_from_vscsi_to_npiv_within_or_different_frames
Ibm i series_lpar_migration_from_vscsi_to_npiv_within_or_different_framesGobinath Panchavarnam
 
Openstack installation using rdo multi node
Openstack installation using rdo multi nodeOpenstack installation using rdo multi node
Openstack installation using rdo multi nodeNarasimha sreeram
 
Implementation of cisco wireless lan controller (multiple wla ns)
Implementation of cisco wireless lan controller (multiple wla ns)Implementation of cisco wireless lan controller (multiple wla ns)
Implementation of cisco wireless lan controller (multiple wla ns)IT Tech
 
Ato2019 weave-services-istio
Ato2019 weave-services-istioAto2019 weave-services-istio
Ato2019 weave-services-istioLin Sun
 
Weave Your Microservices with Istio
Weave Your Microservices with IstioWeave Your Microservices with Istio
Weave Your Microservices with IstioAll Things Open
 
All Things Open 2019 weave-services-istio
All Things Open 2019 weave-services-istioAll Things Open 2019 weave-services-istio
All Things Open 2019 weave-services-istioLin Sun
 
Mikro tik site to site eoip tunnel with i psec
Mikro tik site to site eoip tunnel with i psecMikro tik site to site eoip tunnel with i psec
Mikro tik site to site eoip tunnel with i psecUttam Ds
 
Sharing-Knowledge-OAM-3G-Ericsson .ppt
Sharing-Knowledge-OAM-3G-Ericsson   .pptSharing-Knowledge-OAM-3G-Ericsson   .ppt
Sharing-Knowledge-OAM-3G-Ericsson .pptwafawafa52
 
CCNA Connecting NetworksSA ExamLab 13 CCNA Connecting Netwo.docx
CCNA Connecting NetworksSA ExamLab 13 CCNA Connecting Netwo.docxCCNA Connecting NetworksSA ExamLab 13 CCNA Connecting Netwo.docx
CCNA Connecting NetworksSA ExamLab 13 CCNA Connecting Netwo.docxketurahhazelhurst
 

Ähnlich wie Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding) (20)

Open-E DSS V6 MPIO with ESXi 4.x
Open-E DSS V6 MPIO with ESXi 4.xOpen-E DSS V6 MPIO with ESXi 4.x
Open-E DSS V6 MPIO with ESXi 4.x
 
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft WindowsHow to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
 
Open-E Backup to iSCSI Target Volume over a LAN
Open-E Backup to iSCSI Target Volume over a LANOpen-E Backup to iSCSI Target Volume over a LAN
Open-E Backup to iSCSI Target Volume over a LAN
 
Automating auto-scaled load balancer based on linux and vm orchestrator
Automating auto-scaled load balancer based on linux and vm orchestratorAutomating auto-scaled load balancer based on linux and vm orchestrator
Automating auto-scaled load balancer based on linux and vm orchestrator
 
Vpn
VpnVpn
Vpn
 
Network Automation Tools
Network Automation ToolsNetwork Automation Tools
Network Automation Tools
 
Linux router
Linux routerLinux router
Linux router
 
Nat 03
Nat 03Nat 03
Nat 03
 
Network topology by essay corp uk
Network topology by essay corp ukNetwork topology by essay corp uk
Network topology by essay corp uk
 
Ibm i series_lpar_migration_from_vscsi_to_npiv_within_or_different_frames
Ibm i series_lpar_migration_from_vscsi_to_npiv_within_or_different_framesIbm i series_lpar_migration_from_vscsi_to_npiv_within_or_different_frames
Ibm i series_lpar_migration_from_vscsi_to_npiv_within_or_different_frames
 
Openstack installation using rdo multi node
Openstack installation using rdo multi nodeOpenstack installation using rdo multi node
Openstack installation using rdo multi node
 
Implementation of cisco wireless lan controller (multiple wla ns)
Implementation of cisco wireless lan controller (multiple wla ns)Implementation of cisco wireless lan controller (multiple wla ns)
Implementation of cisco wireless lan controller (multiple wla ns)
 
Ato2019 weave-services-istio
Ato2019 weave-services-istioAto2019 weave-services-istio
Ato2019 weave-services-istio
 
Weave Your Microservices with Istio
Weave Your Microservices with IstioWeave Your Microservices with Istio
Weave Your Microservices with Istio
 
All Things Open 2019 weave-services-istio
All Things Open 2019 weave-services-istioAll Things Open 2019 weave-services-istio
All Things Open 2019 weave-services-istio
 
Mikro tik site to site eoip tunnel with i psec
Mikro tik site to site eoip tunnel with i psecMikro tik site to site eoip tunnel with i psec
Mikro tik site to site eoip tunnel with i psec
 
Linux Telephony
Linux TelephonyLinux Telephony
Linux Telephony
 
Basic configuration access point (1)
Basic configuration access point (1)Basic configuration access point (1)
Basic configuration access point (1)
 
Sharing-Knowledge-OAM-3G-Ericsson .ppt
Sharing-Knowledge-OAM-3G-Ericsson   .pptSharing-Knowledge-OAM-3G-Ericsson   .ppt
Sharing-Knowledge-OAM-3G-Ericsson .ppt
 
CCNA Connecting NetworksSA ExamLab 13 CCNA Connecting Netwo.docx
CCNA Connecting NetworksSA ExamLab 13 CCNA Connecting Netwo.docxCCNA Connecting NetworksSA ExamLab 13 CCNA Connecting Netwo.docx
CCNA Connecting NetworksSA ExamLab 13 CCNA Connecting Netwo.docx
 

Mehr von open-e

Description of Open-E Snapshot
Description of Open-E SnapshotDescription of Open-E Snapshot
Description of Open-E Snapshotopen-e
 
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...
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 DSS V6 How to Setup iSCSI Failover with XenServerOpen-E DSS V6 How to Setup iSCSI Failover with XenServer
Open-E DSS V6 How to Setup iSCSI Failover with XenServeropen-e
 
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...
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 DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...
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 DSS Synchronous Volume Replication over a WANOpen-E DSS Synchronous Volume Replication over a WAN
Open-E DSS Synchronous Volume Replication over a WANopen-e
 
Open-E Backup to Attached Tape Library
Open-E Backup to Attached Tape LibraryOpen-E Backup to Attached Tape Library
Open-E Backup to Attached Tape Libraryopen-e
 
Backup of Data Residing on DSS V6 with Backup Exec
Backup of Data Residing on DSS V6 with Backup ExecBackup of Data Residing on DSS V6 with Backup Exec
Backup of Data Residing on DSS V6 with Backup Execopen-e
 

Mehr von open-e (8)

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

Kürzlich hochgeladen

Generative AI for Technical Writer or Information Developers
Generative AI for Technical Writer or Information DevelopersGenerative AI for Technical Writer or Information Developers
Generative AI for Technical Writer or Information DevelopersRaghuram Pandurangan
 
Advanced Computer Architecture – An Introduction
Advanced Computer Architecture – An IntroductionAdvanced Computer Architecture – An Introduction
Advanced Computer Architecture – An IntroductionDilum Bandara
 
Transcript: New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024Transcript: New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024BookNet Canada
 
Streamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupStreamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupFlorian Wilhelm
 
How to write a Business Continuity Plan
How to write a Business Continuity PlanHow to write a Business Continuity Plan
How to write a Business Continuity PlanDatabarracks
 
Unleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubUnleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubKalema Edgar
 
Commit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyCommit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyAlfredo García Lavilla
 
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024BookNet Canada
 
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptxThe Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptxLoriGlavin3
 
DevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenDevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenHervé Boutemy
 
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptxThe Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptxLoriGlavin3
 
Connect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck PresentationConnect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck PresentationSlibray Presentation
 
DSPy a system for AI to Write Prompts and Do Fine Tuning
DSPy a system for AI to Write Prompts and Do Fine TuningDSPy a system for AI to Write Prompts and Do Fine Tuning
DSPy a system for AI to Write Prompts and Do Fine TuningLars Bell
 
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
Digital Identity is Under Attack: FIDO Paris Seminar.pptxDigital Identity is Under Attack: FIDO Paris Seminar.pptx
Digital Identity is Under Attack: FIDO Paris Seminar.pptxLoriGlavin3
 
SALESFORCE EDUCATION CLOUD | FEXLE SERVICES
SALESFORCE EDUCATION CLOUD | FEXLE SERVICESSALESFORCE EDUCATION CLOUD | FEXLE SERVICES
SALESFORCE EDUCATION CLOUD | FEXLE SERVICESmohitsingh558521
 
Unraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfUnraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfAlex Barbosa Coqueiro
 
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptxMerck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptxLoriGlavin3
 
What is DBT - The Ultimate Data Build Tool.pdf
What is DBT - The Ultimate Data Build Tool.pdfWhat is DBT - The Ultimate Data Build Tool.pdf
What is DBT - The Ultimate Data Build Tool.pdfMounikaPolabathina
 
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek SchlawackFwdays
 

Kürzlich hochgeladen (20)

Generative AI for Technical Writer or Information Developers
Generative AI for Technical Writer or Information DevelopersGenerative AI for Technical Writer or Information Developers
Generative AI for Technical Writer or Information Developers
 
Advanced Computer Architecture – An Introduction
Advanced Computer Architecture – An IntroductionAdvanced Computer Architecture – An Introduction
Advanced Computer Architecture – An Introduction
 
Transcript: New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024Transcript: New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
 
Streamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupStreamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project Setup
 
How to write a Business Continuity Plan
How to write a Business Continuity PlanHow to write a Business Continuity Plan
How to write a Business Continuity Plan
 
DMCC Future of Trade Web3 - Special Edition
DMCC Future of Trade Web3 - Special EditionDMCC Future of Trade Web3 - Special Edition
DMCC Future of Trade Web3 - Special Edition
 
Unleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubUnleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding Club
 
Commit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyCommit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easy
 
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
 
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptxThe Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
 
DevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenDevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache Maven
 
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptxThe Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
 
Connect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck PresentationConnect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck Presentation
 
DSPy a system for AI to Write Prompts and Do Fine Tuning
DSPy a system for AI to Write Prompts and Do Fine TuningDSPy a system for AI to Write Prompts and Do Fine Tuning
DSPy a system for AI to Write Prompts and Do Fine Tuning
 
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
Digital Identity is Under Attack: FIDO Paris Seminar.pptxDigital Identity is Under Attack: FIDO Paris Seminar.pptx
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
 
SALESFORCE EDUCATION CLOUD | FEXLE SERVICES
SALESFORCE EDUCATION CLOUD | FEXLE SERVICESSALESFORCE EDUCATION CLOUD | FEXLE SERVICES
SALESFORCE EDUCATION CLOUD | FEXLE SERVICES
 
Unraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfUnraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdf
 
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptxMerck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
 
What is DBT - The Ultimate Data Build Tool.pdf
What is DBT - The Ultimate Data Build Tool.pdfWhat is DBT - The Ultimate Data Build Tool.pdf
What is DBT - The Ultimate Data Build Tool.pdf
 
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
 

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