how do I use bonded NICs for backups to ReadyNAS?

Hello Morob118two,

Please see this article that might help. Also, make sure the switch/router where you are connecting the NAS supports LACP.

Welcome to the community!

Regards,

---

Morob118two wrote:

how do I select this bond as the default IP for the backup? I know it's a very noob question.can you explicitly make nfs or iscsi go over this bond? obviously I dont want to use the mgmt ip of .50 it is too slow.

 

---

Actually it's an excellent question. 

When you are backing up to the NAS, all you need to do is specify the IP address for the bond (192.168.100.48).  That will direct all the traffic going into the NAS to use the teamed interface.  If you want to use hostnames, you can of course create different DNS names for the two addresses.

In the other direction you have much less control.  The NAS could choose to send traffic over 192.168.100.50 and there isn't much you can do about it.  The needed linux tools aren't built into the NAS (and you'd need to implement that kind of routing with ssh, since there's no support for it in the web ui).

You could create a vlan (with your switches), and shift the management plane into a different IP address space (walled off from the main network).  That would keep data traffic off the management interface.  That might complicate your overall management though.

your simplest solution is to access the admin interface via the bond ip and unplug the gbit link.

alternatively you can put the admin link on a different subnet, you don't necessarily need a dedicated vlan.

IE put admin on 10.x.x.x or 192.168.200.50, of course then you would need to use a computer with an ip also in this admin range (or use internal routes or vlans on your network).

Why not just disconnect the gigabit link? I thought the management interface would work on 10 gigabit links on any ReadyNAS that supported them.