On a clean install adding MACs just seems to loop without getting a form about ixp-manager HOT 7 CLOSED

MACs are populated by an (as yet undocumented) script. This will be added and documented in time. There is currently no facility to add / edit / delete MACs. This is (currently) meant as a read only table.

from ixp-manager.

OK - thanks for the explanation. I might try to help with adding the facility if it isn't too complex (I've been experimenting with IXP-Manager for only 1 day and my PHP-fu is slightly rusty at the moment). To save me searching for where to start, if you could tell me which file(s)/function(s) to start looking in that would help, thanks.

from ixp-manager.

As it turns out, this may be something we need to do ourselves.

What's your use case - do you hard code static MACs on ports for your members? At the moment we're using port security with dynamic MAC learning but are considering the move to static.

We'd also need to examine how we'd handle LAGs.

from ixp-manager.

turns out port security with dynamic learning has several interesting failure modes which is pushing inex into going down the road of using statically configured mac addresses. At the moment, you would use the update-l2database script to populate the macaddress table in the database - this script reads entries directly from the switches. I'll get to documenting this shortly, but if you want to play with it in the interim, make sure that your switch port names exactly match what SNMP reports in the ifDescr field and it should work.

from ixp-manager.

Sorry for the late reply to your question about use-case @barryo, I had to wait for the info from our router-admin team. Here is what they sent me:

We are not using static entries on ports. For the time being we are
using dynamic MAC learning protecting our network from loops with L2
access lists. Due to hardware limitations (line cards we are using on
our extreme switch [model BD-8806] does not support egress access-lists)
we consider using the fdb limit-learning in conjunction with mac lock
timeout timer in order to allow only bgp peers router mac addresses.
We are also using with some providers LAG with LACP configuration.

I hope that is useful...? Please let me know if you would like to know any more details.

from ixp-manager.

the l2 mac learning script will handle this, but due to some coding sloppiness on my part it won't currently handle Extreme switches. I have recently updated the code to remove this vendor dependency, but it's part of a general overhaul of some of the back-end components and we're not quite ready to commit this to the mainline codebase just yet. Hopefully soon.

from ixp-manager.

This script is adding and working for Extreme:

https://github.com/inex/IXP-Manager/wiki/MAC%20Address%20Database

I'm closing this ticket now as this is a readonly feature. Managing static L2 ACLs is another task entirely.

from ixp-manager.