Hello. I think this should be a fast and easy question/answer.
We are using the provided vmware image and see that the images are using static MAC addresses. Is it a requirement to use static macs?
I'm assuming that the issue is hardware upgrades, and that if you swap the mac address, then you'd have to reconfigure the ethernet device on the guest and point the ethernet configuration to the new mac. Is that the only issue we would see from not having a static mac?
Static MAC.
-
tonyyarusso
- Posts: 1128
- Joined: Wed Mar 03, 2010 12:38 pm
- Location: St. Paul, MN, USA
- Contact:
Re: Static MAC.
I can't think of any other problem offhand at least. It's certainly not a deliberate design decision.
Re: Static MAC.
Are you talking about the address listed under /etc/sysimages/networking-scripts or whatever?
This is AFAIC a bug in CentOS. I've attempted to remove the MAC address and it always comes back. I think the solution I've worked out is to set the mac address to ""(including the quotes.)
From what I can tell this does not set the address, rather it uses this to identify the interface. This causes DHCP to be disabled after the address changes, like a VMWare convert.
As some may claim that having NagiosXI instances share the same MAC is vary un-wise it's only going to cause problems in vary controllable situations. For company X and company Y to actively use the same MAC address is actually vary common. For those unlucky enough to have had issues with two NICs sharing the same MAC this is obvious by how common this actually is.
When/If you have this problem it's likely time to consider deploying VLANs to split up your broadcast domains anyway.
None of this however applies to our VMWare images, VMWare should be taking care that it's MAC address is not already in use and either correct or error on the situation. If VMWare dose not currently handle this gracefully it's a feature request waiting to happen.
This is AFAIC a bug in CentOS. I've attempted to remove the MAC address and it always comes back. I think the solution I've worked out is to set the mac address to ""(including the quotes.)
From what I can tell this does not set the address, rather it uses this to identify the interface. This causes DHCP to be disabled after the address changes, like a VMWare convert.
As some may claim that having NagiosXI instances share the same MAC is vary un-wise it's only going to cause problems in vary controllable situations. For company X and company Y to actively use the same MAC address is actually vary common. For those unlucky enough to have had issues with two NICs sharing the same MAC this is obvious by how common this actually is.
When/If you have this problem it's likely time to consider deploying VLANs to split up your broadcast domains anyway.
None of this however applies to our VMWare images, VMWare should be taking care that it's MAC address is not already in use and either correct or error on the situation. If VMWare dose not currently handle this gracefully it's a feature request waiting to happen.