bonding and vlans. Bonding a vlan interface vs applying vlans to a bond interface
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I see no documentation showing this approach. I see plenty of howto's where you bond up eth0 and eth1 into bond0, then apply vlans to bond0 as bond0.122
Trying to maximize the 10G pipe and get rid of copper and save on fiber port costs. If I can manage to pull a node down and move a vlan to another switch or cable and change it's underlining Ethernet interface, that would be cool.
If we use the bond0.122 method, and have to make a change, it would require a re-configuration of clusterware and a complete cluster outage to make things work on bond1.122