well with the multi-volume failover, then the limitations are manageable!
well with the multi-volume failover, then the limitations are manageable!
Originally Posted by To-M
I´ve got a question with the multi iSCSI Volume Replication. must all the iSCSI Volumes be assigned to the same target, or could the volumes be assigned to different targets for different subnets?
At the moment my network config looks like:
- nic1+nic2= bond0 (management and small NFS-share) 192.168.2. (our LAN)
- nic3 - iSCSI for two vmware-servers 192.168.3. (seperate subnet)
- nic4 -for major iSCSI-Target (for central fileserver) 192.168.10. (I want to activate auto-failover for this Target)
- nic5+nic6 = bond1 (replication) 192.168.6....
What must I change for auto-failover?
Hi ottl05
You do not need the same iSCSI target for the Auto Failover to work as long as your Virtual Ip address are on the same subnet as your host.
Use Nic 4 for the virtual IP
If Nic 5 & 6 are bonded and going from server to server that should be fine.
Tom, what's the significance of the ping_node? There is still something not right about my understanding here and it relates to the requirement of the 2 aux connections.
I need to understand if the aux connections for both nodes in the cluster - must they all reside in the same subnet?
How does each node communicate with the ping_node? Is it through the aux connection? If so - then this means that all of a nodes interfaces they must be in the same subnet as the ping_node.
I ask this because no matter what I do, it always starts in a degraded mode (e.g. running on one Aux connection)
and on the host I must set the virtual IP for the target-server?Originally Posted by To-L
Could I use more Virtual IPs ? For each nic in a subnet (subnet1-LAN, subnet2-for vm)?
and with the actual release I could select more than one iscsi-target for autofailover?