 |
The currently implemented data model allows a port MAC address to be duplicate only on a port of the same device. in other words, any two different devices must not use the same MAC address. To the best of my knowledge, this is consistent with the definition of Ethernet as an IEEE standard (less the special-purpose destination addresses, which are not assigned to ports and thus not documented in RackTables). If you can point to a particular technical specification to support the need to legalize duplicate source addresses, please do so. However, it would take time to relax the database constraint safely. Alternatively, you could make the MAC addresses unique (so long as you seem to be in control of the address value), which would automatically eliminate a space for potential fault if things go wrong and segments that are not bridged now become bridged later. |
 |
MAC address can be duplicated at many times. Each vendor have a pool delegated by IANA https://bugs.racktables.org/view.php?id=2049#c4353 and pools used for special purpose, like https://www.iana.org/go/rfc5798 As reminder, the uniqueness of address MAC must be true at the LLC/MAC level of the OSI Model. At the vendor scale, MAC address are not unique globally, it must be unique in the broadcast domain. About the constraint, we already patch our version, it's not a DB constraint. racktables/inc/database.php <code> function assertUniqueL2Addresses ($db_l2addresses, $my_object_id) </code> On our side, we are reimplementing the function to have better granularity to take care of the MAC address prefix and if ports are linked to the same broadcast domain. |
|
|
Thank you for your comments. It is a bit unfortunate that we were talking past each other, but I have other work to do. |
- Anonymous
