Printable View
Hi,
I read this How-To and i have one question, what is the IP to be used IP for the ISCSI Initiator? The one from bond0 or eth2 ?
I'll implement this solution soon for a Vmware Server on Ubuntu 8.0.4 and two OpenE DSS (actually i have bond0 for iSCSI, bond1 for Public access on my SAN & Server).
Thanks a lot for this great update.
NSC
Dear nsc,
Use the bond IP address.
I'm having a problem with failover. Everything seems to be working, it's just that it refuses to use the auxillary NIC and as such, the failover status is "degraded" Here is my NIC layout
The first NIC is for management
Second NIC is Cross over for replication
Third NIC Unused
Fourth NIc Unused
Fifth NIC iSCSI-Path A
Sixth NIC iSCSI-Path B
I'm using MPIO and do not want to use bonded interfaces. So is it a requirement that all interfaces for failover have to be on the same subnet?
The first NIC is for management
Second NIC is Cross over for replication Third NIC Unused Fourth NIc Unused Fifth NIC iSCSI-Path A Sixth NIC iSCSI-Path B
We recommend the replication be bonded - so for NIC 2 please bond with another available NIC that is Unused. We have thought about this in our development and we strongly support this only. If not bonded for the Replication then this will not be supported. This is for your benefit.
We have not tested with MPIO with regards to the Virtual IP address but I believe you can use the other Unused NIC (4) to set the Virtual IP address and use with MPIO from the host side. NIC example for MPIO should be as follows:
Must configure on server both network adapters to work in different subnets:
for example:
- adapter no1: Ip address: 192.168.2.220, NetMask: 255.255.255.0 (Virtual IP Address)
- adapter no2: Ip address: 192.168.3.220, NetMask: 255.255.255.0 (Virtual IP Address)
and the configuration of the client network adapters:
- adapter no1: Ip address: 192.168.2.221, NetMask: 255.255.255.0
- adapter no2: Ip address: 192.168.3.221, NetMask: 255.255.255.0
Thanks very much. Our MPIO is on the host side.
What about this question: do all NICs for failover have to be on the same subnet? Or should all NICs be able to reach the ping node?
Dear enealDC,
The Virtual IP should be on the same subnet, as well as the ping node. And the Replication should be on its own subnet.
Regards,
SJ
Hello,Quote:
Originally Posted by To-M
I used the above guide to setup autofailover, but everytime I try to enable a task on the primary node it says "Most probably there has been an error when connecting to the other node, or one of the selected tasks does not have a counterpart (a reverse task) on the other node. Please check the secondary node address and make sure you have configured appropriate reverse tasks."
eth4+5 are in bonding mode, eth3 is the auxiliary interface for replication and heartbeat. the bond (eth4+5) do have a public ip address, eth3 a private (10.0.0.x). Pinging between both servers using the private address and also the replication do work fine. What could be the problem?
Thanks
I'm still struggling to understand how the auxillary interfaces should be configured.
Someone please help me here. Should the auxiliary interfaces be in the same subnet; because otherwise they both will not be able to reach the ping_node! And if you configure both interfaces in the same subnet, you get a warning!
Also - here is an additional question. In light of the 4TB limitation for replication, is open-E vigorously working on solution for failing over multiple iSCSI volumes? I don't mean to state the obvious, but these limitations really make this feature hard to use. Lets say that i have a 16TB DSS license and I need to provide some redundancy for that entire 16TB. I have to create 4, 4TB volumes but then I have to choose which volume I will provide redundancy for. That's a really tough choice to make. I don't want to undermine the achievement of failover. We are very thankful for it. I do however want to urge you guys not to rest however because we really need to tie everything together. I didn't ever care about the 4TB restriction for replication until I realized that I could only provide redundancy for 4TB in a system that holds 6TB for example...
We will have multi iSCSI Volume Replication in next release during the week of the 17th.
We do recognize the 4TB limitation and we are looking into this please allow us more time for the developers to research this and hopefully without additional cost.
Auxiliary connection is additional connection used for the cluster communication and checking if second node is ok. Please set for both Public and Replication NIC's.
I did, but that doesn't change anything. I just can't select an iSCSI Task as a Failover Task.Quote:
Originally Posted by To-M
well with the multi-volume failover, then the limitations are manageable!
Quote:
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)
Hi enealDC
The Ping node is used for the failover connection management. It could be anything with an IP address that is close to the servers. The servers will ping the ping node to ensure the servers and the path are up and running.
The Aux connection does not need to be on the same subnet as the ping node
Sorry, but I didnt get around with my problem. When trying to assign a iSCSI task to a Failover task it always says:
"Most probably there has been an error when connecting to the other node, or one of the selected tasks does not have a counterpart (a reverse task) on the other node. Please check the secondary node address and make sure you have configured appropriate reverse tasks."
What could be the problem?
Both servers are connected through crossover. IP of the primary host is 10.0.0.30 and IP of the secondary host is 10.0.0.31.
Thanks!
Hi juelz
Did you enter the correct mirror IP address for primary and secondary server?
CONFIGURATION -> Volume Manager -> Vol. replication -> Function: Mirror server IP
On all 4 NIC's have you enabled
Use this network interface to communicate between the nodes.
in SETUP -> Network -> iSCSI Failover -> Function: Auxiliary connection.
so i just need another dss module? do i need to have the same level license as my original? 16tb module with 16tb addon license or do i just need a 16tb module and use the same license on it?Quote:
Originally Posted by To-M
Works perfect over 10Gbit ethernet, incl. fallback en return to primary system. Congratulations, asking for this for over 2 years ;) !!
Quote:
Connection: SyncSource
Total size to replicate: 614400 MB
Remain to replicate: 542078 MB
Speed (avg): 248084 kB/s (216540 kB/s)
Time left: 0:37:17
Source info:
Logical volume: lv0000
Consistency: Consistent
Destination info:
Logical volume: lv0000
Consistency: Inconsistent
IP address: 192.168.50.221
Hi,Quote:
Originally Posted by To-L
replication works perfectly. The status on both volumes is "consistent".
I enabled the "Auxiliary connection" for all NIC's, but I still get the error.
On the primary host it says:
Code:Global status
Service running inactive
Node status inactive
Ping node ok
Communication via:
bond0 unknown
eth3 unknown
eth0 unknown
eth1 unknown
eth2 unknown
When will this new demo cd with auto failover be available?Quote:
Originally Posted by To-M
Dear pfeifferl,
There is no ETA yet for the new demo CD. But it should be ready in a short periode of time.
Regards,
SJ
Weeks ago there was ETA 2 week. And know "no ETA"?? Hmmm ... :confused:Quote:
Originally Posted by Sh-J
We decided to wait until the latest release of DSS which was released on 11-17-08, hopefully we will have this before Monday of next week.
OK, great :)
and on the host I must set the virtual IP for the target-server?Quote:
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?
must the targetname be exactly the same? at the moment on storage1 it is likeQuote:
Originally Posted by To-M
"iqn.2008-04:storage1.target0" and on storage2 like
"iqn.2008-05:storage2.target0"
both have the same alias-name.
Could I assign the LUN on the slave storage (it´s the replication target)?
Q. On the host I must set the virtual IP for the target-server?
A. Host must connect to the Virtual IP Address that you have setup.
Q. Could I use more Virtual IPs ? For each nic in a subnet (subnet1-LAN, subnet2-for vm)?
A. You can setup more Virtual IP's for each NIC but only per NIC assignment.
Note
Virtual IP needs to be unique within its network environment and the same on both nodes (Primary and Secondary).
Changes to virtual IP settings can be done only when failover configuration is not active.
Note
Virtual IP can be in a different subnetwork than the node IPs, e.g. 192.168.2.1 as opposed to 192.168.1.1 and 192.168.1.2.
Q. With the actual release I could select more than one iscsi-target for autofailover?
A. Most recent release DSS 5.0_49 build 3277 allows for more then one iSCSI - Target Auto Failover.
Q. Must the targetname be exactly the same? at the moment on storage1 it is like
"iqn.2008-04:storage1.target0" and on storage2 like
"iqn.2008-05:storage2.target0"
A. Both the Primary and Secondary must have the same Target Name and Lun# and SCSI ID.
- I named the targets equal
- I set up the Virtual IPs on my NICs on both Systems
- the Auxilary is set on all NIC
the status on the primary:
- the ping node: 192.13.47.xxxCode:Names Status
Global status
Service running inactive
Node status inactive
Ping node ok
Communication via:
bond1 unknown (192.168.6... - replication)
eth2 unknown (192.168.10.... - iSCSI )
bond0 unknown (192.13.47.... LAN)
- I entered the IPs from the replication bond as primary and secondary nodes.
but when I activate a iscsi-task for failover I´ll get an error:
Most probably there has been an error when connecting to the other node, or one of the selected tasks does not have a counterpart (a reverse task) on the other node. Please check the secondary node address and make sure you have configured appropriate reverse tasks.
On the secondary I could not setup a replication task, because the Volumes are in target-mode.
So whats wrong?
Are both NIC's for the Replication and Targets have the Auxiliary connection enabled. This is in SETUP -> Network -> iSCSI Failover -> Function: Auxiliary connection
Also check that the Volume Replication is completed successfully in Status > Tasks.
the Auxiliary connection is activated on all NICsQuote:
Originally Posted by To-M
the replication tasks are all completed successfully,
but still the same error.
when I activate the failover-function the information says:
bond0 are the nics to the LAN (192.13.47....)Code:Information
System has automatically selected interface bond0
as primary/secondary node I took the IPs from the replication bond (192.168.6....)
Email me and I will send you a step by step document. It looks as though the secondary has issues. Make sure you have the latest version that was just released this week.
email is underwayQuote:
Originally Posted by To-M
with the help of Todd, the failover is now working :-)
What about the release that was just put up on the FTP server yesterday?
Build 3278. What does this fix?
There was a problem in updating messages in other languages than English and this update fixes the messages updating for the last build 3277. Also fixed problem with error message in Failover/Failback.
Hi,
To-M, can you send the same email, which you send to ottl05, to me? My email address is julian_joswig@web.de
I still experience problems with activating the failover task. I updated the software, but the problem still occurs.
Thanks!
Email has been sent.