Create secondary iscsi nic lagg for failover

[Terry Wilson]

So we have a Dell R710 server running freenas 9.10
Nic's bec0 and bec1 form a LAGG and used for management on a 192.168.1.x subnet

Now we want to take the next available nic (bec2) and assign it to 192.168.13.1
Finally we want to create a LAGG for bec2 (iscsi traffic) and use bce3 in that LAGG


The theory is the mgmt will have a failover NIC and that LAGG will contain bce0, bce1

The iscsi traffic will have a failover NIC and that LAGG will contain bec2, bce3

This way we can segment the traffic (no vlan switch available) from the mgmt traffic and still have some failover on each nic.

Is there a way to accomplish this?

 

[m0nkey_]

You can not assign a NIC that's already in a LAGG. If you put bce0/1 into a LAGG, then they are no longer available for the next LAGG.

 

[Terry Wilson]

You can not assign a NIC that's already in a LAGG. If you put bce0/1 into a LAGG, then they are no longer available for the next LAGG.

yea, understood. What I want to do is see if its possible to create 2 LAGG's
one for mgmt, one for block level iscsi zvol

so
LAGG-1
beco - 192.168.0.7 (mgmt of freenas)
bec1 - failover mode only

LAGG-2
bec2 - 192.168.13.10 (iscsi traffic)
bec3 - failover only

something along those lines...

 

[m0nkey_]

Yes, you should be able to set-up two LAGG interfaces.

When setting up your iSCSI portal, you will need to specify the interface IP address to listen on.

http://doc.freenas.org/9.10/sharing.html#portals

 

[Terry Wilson]

Yes, you should be able to set-up two LAGG interfaces.

When setting up your iSCSI portal, you will need to specify the interface IP address to listen on.

http://doc.freenas.org/9.10/sharing.html#portals

yeah, thats what I figured. What is happening when I create the lagg (failover) is the unit goes offline. I discovered an ARP issue was the reason, rebooted and now I can create the 2 laggs. When in doubt reboot, thats what I have learned about the gui