Andrew, We have an IXP Manager (they just simplified their install a great deal) setup running now for just the metrics. Except for bursty MAX bits feeds it's pretty good (Real max of 25, system shows full burst max at 28 still working on why it's less consistent than our cacti). I am going to attempt a roll out of the Route Servers config additions in the next couple of weekends. Thank you, *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipederson@mankatonetworks.net On Tue, Oct 25, 2016 at 2:05 PM, Andrew Hoyos <hoyosa@gmail.com> wrote:
The folks on NWAX are using IXPManager (https://github.com/inex/IXP- Manager), as well as others. AFAIK, this automates lots of this process (DNS, route-servers, etc) and pulls things from PeeringDB. Might be worth a look.
-- Andrew Hoyos hoyosa@gmail.com
On Oct 25, 2016, at 2:00 PM, Jason Hanke <jayhanke@NEUTRALPATH.NET> wrote:
There is also a peeringDB API.
It might be time for a database driven documentation. Then we could export/import to dns or switch configs.
An online request form might be a good start.
On Tue, Oct 25, 2016 at 1:56 PM, Richard Laager <rlaager@wiktel.com> wrote:
The exchange only cares about the max prefix value if it's larger than our default route server limit of 1000. That's a big network, and I think we've only hit that once. I'm not sure we need to bother getting an explicit number from every network on turn-up.
On the PeeringDB thing... I've thought about that before too. Is *requiring* an entry going too far? I'm on the fence about that.
I see that SIX links the AS number in the participants list to PeeringDB rather than bgp.he.net. I like the bgp.he.net links, but I should see if I can find some place on the list to put a PeeringDB link.
-- Richard
-- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke@neutralpath.net www.neutralpath.net