NAS NFS Failover Replication failing: Error 30

So, we are interested in a NAS Failover solution and I am currently trying to get a test setup of DSS V6 running in two VMs on my local machine using Virtualbox and your how-to Open-E_DSS_V6_NAS_NFS_Failover_over_a_LAN_with_unicast. pdf

I got stuck at page 39 where you are supposed to choose NFS as Failover service, here i get told that "Local or remote volume group does not exist or mirror IP is not configured at least at one node."

Turns out the replication task configured before refuses to work on the secondary node giving an "Error 30: Logical volume is not in source replication mode."
It also says under status->system that the NFS Service has failed on both nodes now.

I can absolutely not figure out where the problem is, the volumes are of the exact same size, the nodes can ping each other perfectly on every of the three subnets, i configured both machines exactly the same and did everything just as described in the how-to up to page 39, well except for the bonding of eth2 and eth3 I just used an eth2...

I also tried it with vmware player, same result. What am I doing wrong here?

Please try to find our webcasts at:
http://www.open-e.com/service-and-su...ts-and-videos/

And look for :
- How to setup iSCSI Failover with Unicast Network connection mode.
And
- Open-E DSS V6 Synchronous Volume Replication with Failover over LAN.

Hi, I just tried with an iscsi replication, as you suggested and get the same problem.
The replication task is always failing on the destination node (i tried switching between both nodes btw.) with an Error 30.

It looks like the _reverse Task does not find a Destination Volume, showing "n/a".

Can you provide us with both systems setup? We need to see what the volume names are and the IP Adresses for the NIC's and the VIP and which are set for the Aux ports.

Primary:
eth0: 192.168.0.211/24 (Aux 192.168.0.212) -> VIP: 192.168.3.210/24
eth1: 192.168.1.211/24 (Aux 192.168.1.212)
eth2: 192.168.2.211/24 (host only)
Volume: lv0100

Secondary:
eth0: 192.168.0.212/24 (Aux 192.168.0.211) -> VIP: 192.168.3.210/24
eth1: 192.168.1.212/24 (Aux 192.168.1.211)
eth2: 192.168.2.212/24 (host only)
Volume: lv0100

Which NIC is the dedicated Volume Replication NIC? Are the Volume Groups the same naming convention like "VG00". Are there VLANs? Can each of the servers ping for all IP's? Do you have more then one gateway for the NICs'?

I chose eth1 for Mirror Server IP on both machines, is that what you mean with dedicated Volume Replication NIC?
Yes the volume groups are both named vg01.
There are no VLANs.
Yes, as I described in my initial post, they can both ping each other on all IPs given.
The NICs actually have no working gateway anymore, because that would be 192.168.3.1 and I wanted to keep them in a different subnet because of the vIP (192.168.3.210) which should be accessible by the other host in the network.

Can you send me a screen shot of both for the Volume Replication tasks for source and destination, just want to make sure that they are set correctly and with the IP's properly set.

Hello again.

The IP settings have been fine the whole time. I had a little help from support and it turns out I misunderstood the whole error 30 thing.

The cause of my initial problem was: I did not have 2 GB free space left on my volume groups...