Nmcli issue with duplicate MAC addresses after bonding nic0 and nic4
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Nmcli issue with duplicate MAC addresses after bonding nic0 and nic4
Hi I guess my first question is while using Nmcli to configure you networks what tools can you use to view the configuration of the network cards. I know ipconfig is no longer used. ip a is presenting me with a duplicate mac on some servers and not on others
So here is the situation:
OS RH7.3 Latest fully patched Physical server
need to create a bond with LACP using two network cards
As we are forced to use the terminal as the server is physical we manually type in the commands and it works. But when we look back at the server after a reboot we notice the MAC addresses have duplicated on bond0, nic0 and nic4 the mac address is nic0 address. We have it hard coded into nmcli for 802-3-ethernet.mac-address:
Is this a known bug should we be worried about it?
When we do a nmcli ed show nic0 we do see the mac address and it is correct, but when we do ip a we see something different. Shouldn't the bond create its own mac address?
thanks hope this all makes sense. These are enterprise servers as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.