![]() ![]() If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave. The master interfaces uses the address of the current active slave (first enslaved). Works the same as in mode balance-rr/0Įach slave keeps its own MAC address. When aįailover happens and the interface changes to active, its MACĪddress is changed to be the master MAC address. MAC address, so all backup interfaces remains unchanged. ![]() The master interface MACĪddress changes during the failover to be the address of currentįollow or 2 - The master interface uses the first enslavement interface MACĪddress to start, but subsequent enslavements keeps the original The MACĪddress is configured at the enslavement.Īctive or 1 - Each slave keeps its own MAC address. Some of the commands might not be accurate because I write this from my phone using my memory but I think you know what I meant, just don't suggest that a typo or syntax error was the problem.None or 0 - default behavior, all slaves use the same MAC address. I even tried removing the interface (from VMware side) and adding a new one but that didn't help. I tried reboot (many times), and could not find any help on the web. ![]() The strange part is if I remove eth1 from the bond and define it as a simple interface it works just fine! The bond is of course in a fault tolerance mode. Only if I remove and readd eth1 to the bond it works (making eth0 the active) If I add eth0 back again it still doesn't work because eth1 is the active one. I could see on cat /proc/net/bond0 that the two interfaces are in the bond and when eth1 is active it does not work. When I use ifdown eth0 or echo -eth0 > /sys/class/net/bond0/bonding/slaves I lose network connectivity to the bond. I created a bond from two interfaces and it works but only when eth0 is active. I have a red-hat enterprise Linux 6.3 vm (VMware vsphere). ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |