Better LAG support - Githubissues

inex / IXP-Manager

Full stack web application powering peering at over 200 Internet Exchange Points (IXPs) globally.

https://www.ixpmanager.org/

GNU General Public License v2.0

377 stars 161 forks source link

Better LAG support #126

Closed nickhilliard closed 8 years ago

nickhilliard commented 10 years ago

At the moment, there is no support for handling LAGs at an interface level. LAGs only work on kit that doesn't use pseudointerfaces for the ethernet bundle.

This improvement will touch several areas of the code, including back-end SQL queries, some front-end stuff, l2database and possibly also graphing code.

bcix commented 10 years ago

Very good to have this open :-)

I will go in review in the BCIX installation for this. As far as I remember now If found missing support at least in update-l2database.pl and the p2p frontend visualization.

We also have customers with multiple LAGs (or ports) in the same peering VLAN, this ist currently at least not supported in the p2p frontend visualization.

listerr commented 10 years ago

+1 for this :)

A virtual interface needs to have an extra field/tag to give the LAG a "Name" and also maybe SNMP OID in its own right (for Cisco type switches where the LAG has its own interface.)

For Extreme/Brocade etc, then there needs to be a way to identify which port in the LAG is configured as the "primary" port in the LAG. (So if we create config for the switch for example, we know which port to apply the changes to, as the switch will not allow changes to the secondary LAG ports.)

listerr commented 10 years ago

Okay, so in the "Advanced" settings which I never use, there is the following:

Virtual Interface Name: Channel Group Number:

But because I don't use these with Extreme, I don't know how well this is supported in the code. So it's just the extra steps to add these as ports/SNMP graphs in their own right.

barryo commented 10 years ago

The advanced settings are legacy and not used any more. They should really be re-examined / removed.

nickhilliard commented 10 years ago

we need to leave the virtual interface name there and use that as the basis for better LAG support.

barryo commented 10 years ago

We've just pushed code to generate aggregate graphs per LAG - live in v.3.6.15.

pdxmaverick commented 10 years ago

I have just update our installation. The lag port graphs are nice for the member. Still hoping to see this in p2p graphs. We have one member that is getting ready to add their third 10g port to a lag. It would be awesome to see where all of this traffic is going across the fabric. I assume the next step is to get the mac address in l2database. Please let me know what I can do to help.

fooelisa commented 9 years ago

Submitted https://github.com/inex/IXP-Manager/pull/199 This fixes p2p stats on LAGs with MACs behind the logical interface for me.

nickhilliard commented 8 years ago

confirmed working on arista kit. Should also be fine on Dell/Cisco.