SlideShare uma empresa Scribd logo
1 de 53
Baixar para ler offline
Step-by-Step Guide
to configure

Open-E DSS V7 Active-Active iSCSI Failover
on Intel Server Systems R2224GZ4GC4
Software Version: DSS ver. 7.00 up01

Presentation updated: April 2013

www.open-e.com

1
Open-E DSS V7 Active-Active iSCSI Failover
TECHNICAL SPECIFICATIONS OF THE INTEL SERVER SYSTEM R2224GZ4GC4 USED DURING TESTS ARE LISTED BELOW:

Model

Intel Server System R2224GZ4GC4

Operating system

Open-E DSS V7

Enclosure/chassis

Intel R2224 2U Chassis

CPU

Intel Xeon E5-2643 3.30GHz

Motherboard

Intel Server Board S2600GZ

Memory

8x 4GB DDR3 1600 ECC-REG Kingston KVR16R11D8/4

Network

1GbE Intel I350 Quad Port Ethernet Controller (on-board)

Network

10GbE Intel AXX10GBNIAIOM Dual Port I/O Module (i82599EB)

HW RAID

Intel Integrated RAID Module RMS25PB080

Hard disk drives

24x 900GB Western Digital WD9001BKHG-02D22V1

Hard disk drives

100GB Intel 710 Series SSDSA2BZ100G301

NOTE:
Presented Intel server is an example. Other Intel servers could be used for the purpose of this configuration.

www.open-e.com

2
Open-E DSS V7 Active-Active iSCSI Failover

TO SET UP ACTIVE-ACTIVE ISCSI FAILOVER ON INTEL SERVER
SYSTEMS R2224GZ4GC4, GO THROUGH 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

3
Open-E DSS V7 Active-Active iSCSI Failover
Storage client 1

IP:192.168.0.101

1. Hardware Configuration

Storage client 2

eth0

eth0 IP:192.168.0.102

IP:192.168.21.101
eth2 (MPIO)
IP:192.168.22.101

eth2 (MPIO)

PING NODES

IP:192.168.31.101
eth3 (MPIO)
IP:192.168.32.101

eth3 (MPIO) IP:192.168.31.102
IP:192.168.32.102

IP Addresses : 192.168.1.107,
192.168.2.107

Data Server (DSS2)

Data Server (DSS1)

node-a (Intel Server System R2224GZ4GC4)
Note:
Please use external tool to
monitor failures in connections
between switches.

eth0

Storage Client Access, Multipath
Auxiliary connection (Heartbeat)
IP:192.168.1.220

(eth1, eth2)

IP:192.168.2.220

(eth3, eth4)

Volume Replication,
Auxilliary connection (Heartbeat)
IP:192.168.5.220
Volume Groups (vg00)
iSCSI volumes (lv0000, lv0001)

Switch 2

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)

iSCSI targets

RAID System 2

RSTP/Port Trunk

Port used for WEB GUI management

bond1

IP Address:192.168.0.221

Switch 1

RAID System 1
IP:192.168.0.220

eth5

node-b

(Intel Server System R2224GZ4GC4)

IP Address:192.168.0.220

bond0

IP:192.168.21.102
IP:192.168.22.102

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 10Gb
connection for the volume replication. Optionally Round-Robin-Bonding with 1Gb
or 10Gb 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

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

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

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

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 field Adress IP 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

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

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

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. Then, 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

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

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

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

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

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

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

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

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

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 Blocks I/O
are now configured.

iSCSI volume (lv0000) is set to source

iSCSI volume (lv0001) is set to destination

www.open-e.com

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

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

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 case of a 10GbE connection it is
recommended to set for the
replication a higher Bandwidth for
SyncSource (MB). To achieve
better performance you can set
500MB. In the example, maximum
600MB is used. Next, click the
create button.
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

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

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
function, information is available on
currently running replication tasks.
When a task is started, a date and
time will appear.

www.open-e.com

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
MirrorTask-a) 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

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 of a
minimum of 500 MB. In our
example 600 MB is used. Next
click the create button.
www.open-e.com

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:
MirrorTask-b.
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

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

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

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.2012-09:mirror-0 ->
lv0000) and click the
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
on node-b.

WARNING:
Please do not switch on the write back (WB) cache !

www.open-e.com

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.2012-09:mirror-1->
lv0001) and click the
button
located under Action.

NOTE:
Both systems must have the same SCSI ID and LUN#

WARNING:
Please do not switch on the write back (WB) cache !

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

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

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

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.2012-09:mirror-0 ->
lv0000) and click the
button
located under Action.
NOTE:
Before clicking the
button again, please
copy & paste the SCSI ID and LUN#
from the node-b.

WARNING:
Please do not switch on the write back cache (WB) !

www.open-e.com

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.2012-09:mirror-1->
lv0001) and click the
button
located under Action.
NOTE:
Before clicking the
button again, please
copy & paste the SCSI ID and LUN#
from the node-b.

WARNING:
Please do not switch on the write back cache (WB) !

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

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

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

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

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

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

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

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

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

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

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

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

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 target: 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

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

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

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

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

52
Open-E DSS V7 Active-Active iSCSI Failover

Thank you!

Follow Open-E:
www.open-e.com

53

Mais conteúdo relacionado

Mais procurados

CONFidence 2017: Hacking embedded with OpenWrt (Vladimir Mitiouchev)
CONFidence 2017: Hacking embedded with OpenWrt (Vladimir Mitiouchev)CONFidence 2017: Hacking embedded with OpenWrt (Vladimir Mitiouchev)
CONFidence 2017: Hacking embedded with OpenWrt (Vladimir Mitiouchev)PROIDEA
 
第6讲 操作与配置Cisco Ios
第6讲 操作与配置Cisco Ios第6讲 操作与配置Cisco Ios
第6讲 操作与配置Cisco IosF.l. Yu
 
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
 
SR-IOV, KVM and Intel X520 10Gbps cards on Debian/Stable
SR-IOV, KVM and Intel X520 10Gbps cards on Debian/StableSR-IOV, KVM and Intel X520 10Gbps cards on Debian/Stable
SR-IOV, KVM and Intel X520 10Gbps cards on Debian/Stablejuet-y
 
Building a Converged Infrastructure based on FCoE, Dell Blades and Force10 sw...
Building a Converged Infrastructure based on FCoE, Dell Blades and Force10 sw...Building a Converged Infrastructure based on FCoE, Dell Blades and Force10 sw...
Building a Converged Infrastructure based on FCoE, Dell Blades and Force10 sw...juet-y
 
Slideshare - PCIe
Slideshare - PCIeSlideshare - PCIe
Slideshare - PCIeJin Wu
 
Howto exportandimportstatisti
Howto exportandimportstatistiHowto exportandimportstatisti
Howto exportandimportstatistisivacse09
 
44CON 2014 - Stupid PCIe Tricks, Joe Fitzpatrick
44CON 2014 - Stupid PCIe Tricks, Joe Fitzpatrick44CON 2014 - Stupid PCIe Tricks, Joe Fitzpatrick
44CON 2014 - Stupid PCIe Tricks, Joe Fitzpatrick44CON
 
使用XMPP進行遠端設備控制
使用XMPP進行遠端設備控制使用XMPP進行遠端設備控制
使用XMPP進行遠端設備控制艾鍗科技
 

Mais procurados (20)

Linux router
Linux routerLinux router
Linux router
 
Log
LogLog
Log
 
CONFidence 2017: Hacking embedded with OpenWrt (Vladimir Mitiouchev)
CONFidence 2017: Hacking embedded with OpenWrt (Vladimir Mitiouchev)CONFidence 2017: Hacking embedded with OpenWrt (Vladimir Mitiouchev)
CONFidence 2017: Hacking embedded with OpenWrt (Vladimir Mitiouchev)
 
第6讲 操作与配置Cisco Ios
第6讲 操作与配置Cisco Ios第6讲 操作与配置Cisco Ios
第6讲 操作与配置Cisco Ios
 
Whatsnew
WhatsnewWhatsnew
Whatsnew
 
Hadoop Cluster - Basic OS Setup Insights
Hadoop Cluster - Basic OS Setup InsightsHadoop Cluster - Basic OS Setup Insights
Hadoop Cluster - Basic OS Setup Insights
 
Netmiko library
Netmiko libraryNetmiko library
Netmiko library
 
Log
LogLog
Log
 
SR-IOV, KVM and Intel X520 10Gbps cards on Debian/Stable
SR-IOV, KVM and Intel X520 10Gbps cards on Debian/StableSR-IOV, KVM and Intel X520 10Gbps cards on Debian/Stable
SR-IOV, KVM and Intel X520 10Gbps cards on Debian/Stable
 
Building a Converged Infrastructure based on FCoE, Dell Blades and Force10 sw...
Building a Converged Infrastructure based on FCoE, Dell Blades and Force10 sw...Building a Converged Infrastructure based on FCoE, Dell Blades and Force10 sw...
Building a Converged Infrastructure based on FCoE, Dell Blades and Force10 sw...
 
Network commands
Network commandsNetwork commands
Network commands
 
Linux network tools (Maarten Blomme)
Linux network tools (Maarten Blomme)Linux network tools (Maarten Blomme)
Linux network tools (Maarten Blomme)
 
QNAP Selection Guide 2015
QNAP Selection Guide 2015QNAP Selection Guide 2015
QNAP Selection Guide 2015
 
Slideshare - PCIe
Slideshare - PCIeSlideshare - PCIe
Slideshare - PCIe
 
Howto exportandimportstatisti
Howto exportandimportstatistiHowto exportandimportstatisti
Howto exportandimportstatisti
 
44CON 2014 - Stupid PCIe Tricks, Joe Fitzpatrick
44CON 2014 - Stupid PCIe Tricks, Joe Fitzpatrick44CON 2014 - Stupid PCIe Tricks, Joe Fitzpatrick
44CON 2014 - Stupid PCIe Tricks, Joe Fitzpatrick
 
Whats new
Whats newWhats new
Whats new
 
Log
LogLog
Log
 
使用XMPP進行遠端設備控制
使用XMPP進行遠端設備控制使用XMPP進行遠端設備控制
使用XMPP進行遠端設備控制
 
Barios crosober
Barios crosoberBarios crosober
Barios crosober
 

Destaque

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
 
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
 
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 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
 
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
 
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
 
Description of Open-E Snapshot
Description of Open-E SnapshotDescription of Open-E Snapshot
Description of Open-E Snapshotopen-e
 
Open-E DSS V7 Active-Passive iSCSI Failover
Open-E DSS V7 Active-Passive iSCSI FailoverOpen-E DSS V7 Active-Passive iSCSI Failover
Open-E DSS V7 Active-Passive iSCSI Failoveropen-e
 

Destaque (8)

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
 
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...
 
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 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
 
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
 
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
 
Description of Open-E Snapshot
Description of Open-E SnapshotDescription of Open-E Snapshot
Description of Open-E Snapshot
 
Open-E DSS V7 Active-Passive iSCSI Failover
Open-E DSS V7 Active-Passive iSCSI FailoverOpen-E DSS V7 Active-Passive iSCSI Failover
Open-E DSS V7 Active-Passive iSCSI Failover
 

Semelhante a Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems

Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)open-e
 
SR-IOV, KVM and Emulex OneConnect 10Gbps cards on Debian/Stable
SR-IOV, KVM and Emulex OneConnect 10Gbps cards on Debian/StableSR-IOV, KVM and Emulex OneConnect 10Gbps cards on Debian/Stable
SR-IOV, KVM and Emulex OneConnect 10Gbps cards on Debian/Stablejuet-y
 
Konfigurasi Server Gateway dengan fitur PROXY, WEBSERVER dan DHCP
Konfigurasi Server Gateway dengan fitur PROXY, WEBSERVER dan DHCPKonfigurasi Server Gateway dengan fitur PROXY, WEBSERVER dan DHCP
Konfigurasi Server Gateway dengan fitur PROXY, WEBSERVER dan DHCPWalid Umar
 
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
 
All contents are Copyright © 1992–2012 Cisco Systems, Inc. A.docx
All contents are Copyright © 1992–2012 Cisco Systems, Inc. A.docxAll contents are Copyright © 1992–2012 Cisco Systems, Inc. A.docx
All contents are Copyright © 1992–2012 Cisco Systems, Inc. A.docxgalerussel59292
 
Network topology by essay corp uk
Network topology by essay corp ukNetwork topology by essay corp uk
Network topology by essay corp ukJohnsmith5188
 
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
 
LF_OVS_17_OVS-DPDK Installation and Gotchas
LF_OVS_17_OVS-DPDK Installation and GotchasLF_OVS_17_OVS-DPDK Installation and Gotchas
LF_OVS_17_OVS-DPDK Installation and GotchasLF_OpenvSwitch
 
HeroLympics Eng V03 Henk Vd Valk
HeroLympics  Eng V03 Henk Vd ValkHeroLympics  Eng V03 Henk Vd Valk
HeroLympics Eng V03 Henk Vd Valkhvdvalk
 
Serial Communication in LabVIEW FPGA on Xilinx Spartan 3E Starter board
Serial Communication in LabVIEW FPGA on Xilinx Spartan 3E Starter boardSerial Communication in LabVIEW FPGA on Xilinx Spartan 3E Starter board
Serial Communication in LabVIEW FPGA on Xilinx Spartan 3E Starter boardVincent Claes
 
Meet the Experts: InfluxDB Product Update
Meet the Experts: InfluxDB Product UpdateMeet the Experts: InfluxDB Product Update
Meet the Experts: InfluxDB Product UpdateInfluxData
 
Detailed explanation of Basic router configuration
Detailed explanation of Basic router configurationDetailed explanation of Basic router configuration
Detailed explanation of Basic router configurationsamreenghauri786
 

Semelhante a Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems (20)

Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
 
Nat 03
Nat 03Nat 03
Nat 03
 
SR-IOV, KVM and Emulex OneConnect 10Gbps cards on Debian/Stable
SR-IOV, KVM and Emulex OneConnect 10Gbps cards on Debian/StableSR-IOV, KVM and Emulex OneConnect 10Gbps cards on Debian/Stable
SR-IOV, KVM and Emulex OneConnect 10Gbps cards on Debian/Stable
 
Konfigurasi Server Gateway dengan fitur PROXY, WEBSERVER dan DHCP
Konfigurasi Server Gateway dengan fitur PROXY, WEBSERVER dan DHCPKonfigurasi Server Gateway dengan fitur PROXY, WEBSERVER dan DHCP
Konfigurasi Server Gateway dengan fitur PROXY, WEBSERVER dan DHCP
 
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
 
Nat 07
Nat 07Nat 07
Nat 07
 
Network Automation Tools
Network Automation ToolsNetwork Automation Tools
Network Automation Tools
 
All contents are Copyright © 1992–2012 Cisco Systems, Inc. A.docx
All contents are Copyright © 1992–2012 Cisco Systems, Inc. A.docxAll contents are Copyright © 1992–2012 Cisco Systems, Inc. A.docx
All contents are Copyright © 1992–2012 Cisco Systems, Inc. A.docx
 
Day 13.1..1 catalyst switch
Day 13.1..1 catalyst switchDay 13.1..1 catalyst switch
Day 13.1..1 catalyst switch
 
Network topology by essay corp uk
Network topology by essay corp ukNetwork topology by essay corp uk
Network topology by essay corp uk
 
Vyos clustering ipsec
Vyos clustering ipsecVyos clustering ipsec
Vyos clustering ipsec
 
Ik
IkIk
Ik
 
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
 
LF_OVS_17_OVS-DPDK Installation and Gotchas
LF_OVS_17_OVS-DPDK Installation and GotchasLF_OVS_17_OVS-DPDK Installation and Gotchas
LF_OVS_17_OVS-DPDK Installation and Gotchas
 
HeroLympics Eng V03 Henk Vd Valk
HeroLympics  Eng V03 Henk Vd ValkHeroLympics  Eng V03 Henk Vd Valk
HeroLympics Eng V03 Henk Vd Valk
 
CCNA Icnd110 s04l04
CCNA Icnd110 s04l04CCNA Icnd110 s04l04
CCNA Icnd110 s04l04
 
Serial Communication in LabVIEW FPGA on Xilinx Spartan 3E Starter board
Serial Communication in LabVIEW FPGA on Xilinx Spartan 3E Starter boardSerial Communication in LabVIEW FPGA on Xilinx Spartan 3E Starter board
Serial Communication in LabVIEW FPGA on Xilinx Spartan 3E Starter board
 
Meet the Experts: InfluxDB Product Update
Meet the Experts: InfluxDB Product UpdateMeet the Experts: InfluxDB Product Update
Meet the Experts: InfluxDB Product Update
 
Detailed explanation of Basic router configuration
Detailed explanation of Basic router configurationDetailed explanation of Basic router configuration
Detailed explanation of Basic router configuration
 
Icnd210 s08l03
Icnd210 s08l03Icnd210 s08l03
Icnd210 s08l03
 

Último

Long journey of Ruby standard library at RubyConf AU 2024
Long journey of Ruby standard library at RubyConf AU 2024Long journey of Ruby standard library at RubyConf AU 2024
Long journey of Ruby standard library at RubyConf AU 2024Hiroshi SHIBATA
 
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
[Webinar] SpiraTest - Setting New Standards in Quality Assurance[Webinar] SpiraTest - Setting New Standards in Quality Assurance
[Webinar] SpiraTest - Setting New Standards in Quality AssuranceInflectra
 
A Framework for Development in the AI Age
A Framework for Development in the AI AgeA Framework for Development in the AI Age
A Framework for Development in the AI AgeCprime
 
Moving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdfMoving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdfLoriGlavin3
 
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024BookNet Canada
 
The State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptxThe State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptxLoriGlavin3
 
QCon London: Mastering long-running processes in modern architectures
QCon London: Mastering long-running processes in modern architecturesQCon London: Mastering long-running processes in modern architectures
QCon London: Mastering long-running processes in modern architecturesBernd Ruecker
 
Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...
Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...
Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...Nikki Chapple
 
Connecting the Dots for Information Discovery.pdf
Connecting the Dots for Information Discovery.pdfConnecting the Dots for Information Discovery.pdf
Connecting the Dots for Information Discovery.pdfNeo4j
 
Varsha Sewlal- Cyber Attacks on Critical Critical Infrastructure
Varsha Sewlal- Cyber Attacks on Critical Critical InfrastructureVarsha Sewlal- Cyber Attacks on Critical Critical Infrastructure
Varsha Sewlal- Cyber Attacks on Critical Critical Infrastructureitnewsafrica
 
So einfach geht modernes Roaming fuer Notes und Nomad.pdf
So einfach geht modernes Roaming fuer Notes und Nomad.pdfSo einfach geht modernes Roaming fuer Notes und Nomad.pdf
So einfach geht modernes Roaming fuer Notes und Nomad.pdfpanagenda
 
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptxPasskey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptxLoriGlavin3
 
Modern Roaming for Notes and Nomad – Cheaper Faster Better Stronger
Modern Roaming for Notes and Nomad – Cheaper Faster Better StrongerModern Roaming for Notes and Nomad – Cheaper Faster Better Stronger
Modern Roaming for Notes and Nomad – Cheaper Faster Better Strongerpanagenda
 
Top 10 Hubspot Development Companies in 2024
Top 10 Hubspot Development Companies in 2024Top 10 Hubspot Development Companies in 2024
Top 10 Hubspot Development Companies in 2024TopCSSGallery
 
Potential of AI (Generative AI) in Business: Learnings and Insights
Potential of AI (Generative AI) in Business: Learnings and InsightsPotential of AI (Generative AI) in Business: Learnings and Insights
Potential of AI (Generative AI) in Business: Learnings and InsightsRavi Sanghani
 
Emixa Mendix Meetup 11 April 2024 about Mendix Native development
Emixa Mendix Meetup 11 April 2024 about Mendix Native developmentEmixa Mendix Meetup 11 April 2024 about Mendix Native development
Emixa Mendix Meetup 11 April 2024 about Mendix Native developmentPim van der Noll
 
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
 
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
 
Zeshan Sattar- Assessing the skill requirements and industry expectations for...
Zeshan Sattar- Assessing the skill requirements and industry expectations for...Zeshan Sattar- Assessing the skill requirements and industry expectations for...
Zeshan Sattar- Assessing the skill requirements and industry expectations for...itnewsafrica
 
Genislab builds better products and faster go-to-market with Lean project man...
Genislab builds better products and faster go-to-market with Lean project man...Genislab builds better products and faster go-to-market with Lean project man...
Genislab builds better products and faster go-to-market with Lean project man...Farhan Tariq
 

Último (20)

Long journey of Ruby standard library at RubyConf AU 2024
Long journey of Ruby standard library at RubyConf AU 2024Long journey of Ruby standard library at RubyConf AU 2024
Long journey of Ruby standard library at RubyConf AU 2024
 
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
[Webinar] SpiraTest - Setting New Standards in Quality Assurance[Webinar] SpiraTest - Setting New Standards in Quality Assurance
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
 
A Framework for Development in the AI Age
A Framework for Development in the AI AgeA Framework for Development in the AI Age
A Framework for Development in the AI Age
 
Moving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdfMoving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdf
 
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
New from BookNet Canada for 2024: Loan Stars - Tech Forum 2024
 
The State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptxThe State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptx
 
QCon London: Mastering long-running processes in modern architectures
QCon London: Mastering long-running processes in modern architecturesQCon London: Mastering long-running processes in modern architectures
QCon London: Mastering long-running processes in modern architectures
 
Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...
Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...
Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...
 
Connecting the Dots for Information Discovery.pdf
Connecting the Dots for Information Discovery.pdfConnecting the Dots for Information Discovery.pdf
Connecting the Dots for Information Discovery.pdf
 
Varsha Sewlal- Cyber Attacks on Critical Critical Infrastructure
Varsha Sewlal- Cyber Attacks on Critical Critical InfrastructureVarsha Sewlal- Cyber Attacks on Critical Critical Infrastructure
Varsha Sewlal- Cyber Attacks on Critical Critical Infrastructure
 
So einfach geht modernes Roaming fuer Notes und Nomad.pdf
So einfach geht modernes Roaming fuer Notes und Nomad.pdfSo einfach geht modernes Roaming fuer Notes und Nomad.pdf
So einfach geht modernes Roaming fuer Notes und Nomad.pdf
 
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptxPasskey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
 
Modern Roaming for Notes and Nomad – Cheaper Faster Better Stronger
Modern Roaming for Notes and Nomad – Cheaper Faster Better StrongerModern Roaming for Notes and Nomad – Cheaper Faster Better Stronger
Modern Roaming for Notes and Nomad – Cheaper Faster Better Stronger
 
Top 10 Hubspot Development Companies in 2024
Top 10 Hubspot Development Companies in 2024Top 10 Hubspot Development Companies in 2024
Top 10 Hubspot Development Companies in 2024
 
Potential of AI (Generative AI) in Business: Learnings and Insights
Potential of AI (Generative AI) in Business: Learnings and InsightsPotential of AI (Generative AI) in Business: Learnings and Insights
Potential of AI (Generative AI) in Business: Learnings and Insights
 
Emixa Mendix Meetup 11 April 2024 about Mendix Native development
Emixa Mendix Meetup 11 April 2024 about Mendix Native developmentEmixa Mendix Meetup 11 April 2024 about Mendix Native development
Emixa Mendix Meetup 11 April 2024 about Mendix Native development
 
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
 
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
 
Zeshan Sattar- Assessing the skill requirements and industry expectations for...
Zeshan Sattar- Assessing the skill requirements and industry expectations for...Zeshan Sattar- Assessing the skill requirements and industry expectations for...
Zeshan Sattar- Assessing the skill requirements and industry expectations for...
 
Genislab builds better products and faster go-to-market with Lean project man...
Genislab builds better products and faster go-to-market with Lean project man...Genislab builds better products and faster go-to-market with Lean project man...
Genislab builds better products and faster go-to-market with Lean project man...
 

Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems

  • 1. Step-by-Step Guide to configure Open-E DSS V7 Active-Active iSCSI Failover on Intel Server Systems R2224GZ4GC4 Software Version: DSS ver. 7.00 up01 Presentation updated: April 2013 www.open-e.com 1
  • 2. Open-E DSS V7 Active-Active iSCSI Failover TECHNICAL SPECIFICATIONS OF THE INTEL SERVER SYSTEM R2224GZ4GC4 USED DURING TESTS ARE LISTED BELOW: Model Intel Server System R2224GZ4GC4 Operating system Open-E DSS V7 Enclosure/chassis Intel R2224 2U Chassis CPU Intel Xeon E5-2643 3.30GHz Motherboard Intel Server Board S2600GZ Memory 8x 4GB DDR3 1600 ECC-REG Kingston KVR16R11D8/4 Network 1GbE Intel I350 Quad Port Ethernet Controller (on-board) Network 10GbE Intel AXX10GBNIAIOM Dual Port I/O Module (i82599EB) HW RAID Intel Integrated RAID Module RMS25PB080 Hard disk drives 24x 900GB Western Digital WD9001BKHG-02D22V1 Hard disk drives 100GB Intel 710 Series SSDSA2BZ100G301 NOTE: Presented Intel server is an example. Other Intel servers could be used for the purpose of this configuration. www.open-e.com 2
  • 3. Open-E DSS V7 Active-Active iSCSI Failover TO SET UP ACTIVE-ACTIVE ISCSI FAILOVER ON INTEL SERVER SYSTEMS R2224GZ4GC4, GO THROUGH 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 3
  • 4. Open-E DSS V7 Active-Active iSCSI Failover Storage client 1 IP:192.168.0.101 1. Hardware Configuration Storage client 2 eth0 eth0 IP:192.168.0.102 IP:192.168.21.101 eth2 (MPIO) IP:192.168.22.101 eth2 (MPIO) PING NODES IP:192.168.31.101 eth3 (MPIO) IP:192.168.32.101 eth3 (MPIO) IP:192.168.31.102 IP:192.168.32.102 IP Addresses : 192.168.1.107, 192.168.2.107 Data Server (DSS2) Data Server (DSS1) node-a (Intel Server System R2224GZ4GC4) Note: Please use external tool to monitor failures in connections between switches. eth0 Storage Client Access, Multipath Auxiliary connection (Heartbeat) IP:192.168.1.220 (eth1, eth2) IP:192.168.2.220 (eth3, eth4) Volume Replication, Auxilliary connection (Heartbeat) IP:192.168.5.220 Volume Groups (vg00) iSCSI volumes (lv0000, lv0001) Switch 2 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) iSCSI targets RAID System 2 RSTP/Port Trunk Port used for WEB GUI management bond1 IP Address:192.168.0.221 Switch 1 RAID System 1 IP:192.168.0.220 eth5 node-b (Intel Server System R2224GZ4GC4) IP Address:192.168.0.220 bond0 IP:192.168.21.102 IP:192.168.22.102 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 10Gb connection for the volume replication. Optionally Round-Robin-Bonding with 1Gb or 10Gb 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 4
  • 5. 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 5
  • 6. 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 6
  • 7. 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 7
  • 8. 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 field Adress IP 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 8
  • 9. 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 9
  • 10. 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 10
  • 11. 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. Then, 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 11
  • 12. 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 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 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 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 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 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 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 15
  • 16. 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 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 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 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 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 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 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 19
  • 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 2 logical iSCSI Volume Blocks I/O are now configured. iSCSI volume (lv0000) is set to source iSCSI volume (lv0001) is set to destination www.open-e.com 20
  • 21. 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 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 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 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 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 case of a 10GbE connection it is recommended to set for the replication a higher Bandwidth for SyncSource (MB). To achieve better performance you can set 500MB. In the example, maximum 600MB is used. Next, click the create button. 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 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 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 In the Replication tasks manager function, information is available on currently running replication tasks. When a task is started, a date and time will appear. www.open-e.com 25
  • 26. 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 MirrorTask-a) 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 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 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 of a minimum of 500 MB. In our example 600 MB is used. Next click the create button. www.open-e.com 27
  • 28. 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: MirrorTask-b. 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 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 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 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 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 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 After that, select target0 within the Targets field. To assign appropriate volume to the target (iqn.2012-09:mirror-0 -> lv0000) and click the 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 on node-b. WARNING: Please do not switch on the write back (WB) cache ! www.open-e.com 31
  • 32. 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.2012-09:mirror-1-> lv0001) and click the button located under Action. NOTE: Both systems must have the same SCSI ID and LUN# WARNING: Please do not switch on the write back (WB) cache ! 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 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 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 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 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 target0 within the Targets field. To assign appropriate volume to the target (iqn.2012-09:mirror-0 -> lv0000) and click the button located under Action. NOTE: Before clicking the button again, please copy & paste the SCSI ID and LUN# from the node-b. WARNING: Please do not switch on the write back cache (WB) ! www.open-e.com 35
  • 36. 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.2012-09:mirror-1-> lv0001) and click the button located under Action. NOTE: Before clicking the button again, please copy & paste the SCSI ID and LUN# from the node-b. WARNING: Please do not switch on the write back cache (WB) ! 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 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 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 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 38
  • 39. 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 39
  • 40. 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 40
  • 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-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 41
  • 42. 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 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, 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 43
  • 44. 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 44
  • 45. 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 45
  • 46. 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 46
  • 47. 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 47
  • 48. 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 target: 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 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 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 49
  • 50. 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 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 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 51
  • 52. 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 52
  • 53. Open-E DSS V7 Active-Active iSCSI Failover Thank you! Follow Open-E: www.open-e.com 53