open-e failover for onapp cloud

[Gr-R]

Make sure the initiators are using the Virtual IP to make the iSCSI connections.
If there are any allow/deny rules or CHAP authentication being used, this needs to be the same on each node to allow proper connectivity.
This may help in the setup :
http://www.open-e.com/library/webcasts-and-videos/
Open-E DSS V6 AutoFailover with VMware 4.0 - Webcast

[cloudtech]

Make sure the initiators are using the Virtual IP to make the iSCSI connections.
If there are any allow/deny rules or CHAP authentication being used, this needs to be the same on each node to allow proper connectivity.
This may help in the setup :
http://www.open-e.com/library/webcasts-and-videos/
Open-E DSS V6 AutoFailover with VMware 4.0 - Webcast

Thanks. I have Virtual IP on Client Storage Access network. Do you mean I need to use the Virtual IP on onapp cloud instead of the actual IP of the Storage Access network? I don't use CHAP authentication.

[Gr-R]

Yes, you need to use the virtualized IP that you et up when configuring the failover, for iSCSI traffic.
The nodes cant move the real NIC IP, we move the virtual IP to the active node.

Watch the video I provided, it will help make it clear.

[cloudtech]

Yes, you need to use the virtualized IP that you et up when configuring the failover, for iSCSI traffic.
The nodes cant move the real NIC IP, we move the virtual IP to the active node.

Watch the video I provided, it will help make it clear.

I just watched the video and found out the answer. Thank you for your support.

[Gr-R]

Glad to help!

[cloudtech]

Sorry to bother you again. I have the following setup, but I am not able to ping the virtual IP from both SAN servers. In the video, I see they can ping each other. Should I setup 192.168.100.254 as gateway? Thanks.

Primary SAN

eth0 - management network - 192.168.1.207
Gateway - 192.168.1.254
eth1 - SAN storage network - 192.168.2.207
eth2 - Replication network - 192.168.3.207

Secondary SAN

eth0 - management network - 192.168.1.208
Gateway - 192.168.1.254
eth1 - SAN storage network - 192.168.2.208
eth2 - Replication network - 192.168.3.208

Virtual IP is on eth1 for both SANs
IP address: 192.168.100.100
Netmask: 255.255.255.0
Broadcast: 192.168.100.255

[Gr-R]

It does seem like your gateway is not handling the virtual IP, and its subnet.
You should check this.
Or, if the failover service is not yet started the Virtual IPs are not up and available yet.