Hello,
how can I define specific NICs for the replication traffic?
We have 2 DSS v6 with each 6 NICs and we want to have 2 NICs dedicated to replication (bond?).
Hello,
how can I define specific NICs for the replication traffic?
We have 2 DSS v6 with each 6 NICs and we want to have 2 NICs dedicated to replication (bond?).
regards,
Lukas
descience.NET
Dr. Lukas Pfeiffer
A-1140 Wien
Austria
www.dotnethost.at
DSS v6 b4550 iSCSI autofailover with Windows 2008 R2 failover cluster (having still some issues with autofailover).
2 DSS: 3HE Supermicro X7DBE BIOS 2.1a, Areca ARC-1261ML FW 1.48, 8x WD RE3 1TB, 1x Intel PRO1000MT Dualport, 1x Intel PRO1000PT Dualport.
2 Windows Nodes: Intel SR1500 + Intel SR1560, Dual XEON E54xx, 32 GB RAM, 6 NICs. Windows Server 2008 R2.
Create your bond interfaces first. In my setup, I have Bond0 for iSCSI traffic, Bond1 for replication, and Bond2 for management. When you set up your bond interface, use ip addresses on the same subnet for both devices, so DSS-A Bond1 is 192.168.1.1 and DSS-B Bond1 is 192.168.1.2.Originally Posted by pfeifferl
Next, under Configuration - Volume Manager - Volume replication, you set up the replication tasks, and that's where you specify the Mirror Server ip address, which is the address of the other DSS unit, so your DSS-A replication tasks will point to 192.168.1.2 and your DSS-B replication tasks (i.e., the reverse replication tasks) will point to 192.168.1.1.
One issue that I ran into was that I had created replication tasks with spaces in the name (i.e., "Volume 0001 replication" and while the task was created and ran, it did not show up in the iSCSI failover configuration. My advice is to create tasks without spaces.
Hope this helps,
James