Contact Us

support@onapp.com

U.S: (+1) 888-876-8666

UK: +44 (0) 203-318-5364

LACP 4 NICS bond (Mode 4) traffic goes through 1 NIC instead of 4

Follow

Comments

5 comments

  • Avatar
    Ken Richardson

    I'm kind of surprised that OnApp would choose a bonding method that isn't supported by most if not all Juniper EX/Cisco Catalyst switches.

  • Avatar
    Ryan Gelobter

    Ken, what method are you referring to, possibly their default balance-rr I think? mode 4/LACP/802.3ad is pretty well supported on Juniper EX/Cisco switches as far as I have seen.

  • Avatar
    Ken Richardson

    balance-rr isn't supported without using cheaper Netgear switches from what I've seen. Even if you do get it working you're at risk of high load on your switch. At least that has been the case with Juniper EX.  802.3ad is supported but OnApp will tell you that it's not recommended.  With that said I've determined that it's not really OnApp's choice since 802.3 has compliance limitations.

    I was only intending on using it temporarily so I just moved on.  Is there a fully tested and proven instance running 802.3ad on an EX/Catalyst?  And without implications such as high load at the switch?

  • Avatar
    Ryan Gelobter

    Ken, I'm not sure what else you are running on your switch but even without OnApp I have done LACP/802.3ad on Cisco 3550/3560G and Juniper EX2200,3200, and 3300 switches and never had any problems with high CPU or instability. We had no problems using 802.3ad for our storage network on a test OnApp setup that has been running for 6-8 months.

    I do find it odd that OnApp invests heavily in their integrated storage but chooses to go down the path of not publishing any recommended ways to setup your network to use it effectively. They tell you in their guides you need more than 1Gbps and you should bond, but its not supported. I understand why but it doesn't make it any easier for those trying to set it up.

  • Avatar
    Ken Richardson

    Correction:  The run up of CPU load issue could occur when using balance-rr due to flapping.

    As for 802.3ad we configured it as we configure all of our LAGs with LACP since we use it on our iSCSI SANs which work flawlessly. Our position was that when OnApp tells us it's "not recommended" and it's related to disk IO that it's not something we wanted to take chances with and we didn't have a long term test environment. 

    Balance-rr with a switch your not likely to want to use in production.  Or... Use a LAG protocol that they put caution tape on. Even this article, which is useful, has a big question mark at the end and you're the first person (I've not looked that hard) that has said that it's working with confidence.

Please sign in to leave a comment.