February 2017 - mice-discuss - lists.micemn.net

Google congestion?

by Andrew Hoyos

Is Google currently 4x10g? Looks like it’s full. We’ve had various customer complaints about youtube stuff not working, and have shut down our peering session with them. -- Andrew Hoyos hoyosa(a)gmail.com

Feb. 21, 2017

Re: BGP Large Communities

by Doug McIntyre

On Fri, Feb 17, 2017 at 03:54:21PM -0600, Jonathan Stewart wrote: > On Fri, Feb 17, 2017 at 12:37 AM, David Farmer <farmer(a)umn.edu> wrote: > > > BIRD 1.6.3 support it, <snip> > > > What version of BIRD is MICE running now? > > We are running 1.6.3, but no members are asking for large BGP community > support yet. Version 1.6.0 -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Feb. 17, 2017

Re: BGP Large Communities

by Jonathan Stewart

On Fri, Feb 17, 2017 at 12:37 AM, David Farmer <farmer(a)umn.edu> wrote: > BIRD 1.6.3 support it, <snip> > What version of BIRD is MICE running now? We are running 1.6.3, but no members are asking for large BGP community support yet. Jonathan MBIX.ca

Feb. 17, 2017

Re: BGP Large Communities

by Andrew Hoyos

> On Feb 17, 2017, at 7:43 AM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > > On Fri, Feb 17, 2017 at 07:25:14AM -0600, Mike Horwath wrote: >> On Fri, Feb 17, 2017 at 12:37:05AM -0600, David Farmer wrote: >>> BIRD 1.6.3 support it, so I'd like to suggest we think about a third route >>> server for testing with BGP Large Communities. If that goes well then >>> phase it in with the production servers maybe toward the end of 2017 when >>> more of the implementations for big iron routers make it in to production >>> code, >>> >>> What do others think? >> >> Quick view: I don't see why upgrading to 1.6.3 and turning it on for >> just folks wanting it could be done - just don't pass them onto other >> users. > > I would think as well just to upgrade the BIRD code all around anyway > at some point, and let people test. AFAIK, the source end has to > enable them and specificly configure them in order to use them. They > haven't fundementally changed anything, just added on new attributes. I’d agree with this as well. This is a relatively low risk upgrade, and don’t see the need to wait or have a third route server. Many IX’s are already running this same code in production. -- Andrew Hoyos hoyosa(a)gmail.com

Feb. 17, 2017

Re: BGP Large Communities

by Doug McIntyre

On Fri, Feb 17, 2017 at 07:25:14AM -0600, Mike Horwath wrote: > On Fri, Feb 17, 2017 at 12:37:05AM -0600, David Farmer wrote: > > BIRD 1.6.3 support it, so I'd like to suggest we think about a third route > > server for testing with BGP Large Communities. If that goes well then > > phase it in with the production servers maybe toward the end of 2017 when > > more of the implementations for big iron routers make it in to production > > code, > > > > What do others think? > > Quick view: I don't see why upgrading to 1.6.3 and turning it on for > just folks wanting it could be done - just don't pass them onto other > users. I would think as well just to upgrade the BIRD code all around anyway at some point, and let people test. AFAIK, the source end has to enable them and specificly configure them in order to use them. They haven't fundementally changed anything, just added on new attributes. Large Communities has already rolled out in most hardware's code, even if the RFC just came out, they've already been doing it in some fashion for a while. https://labs.ripe.net/Members/emileaben/large-bgp-communities-largely-accep… As somebody was discussing with me, there are several ways of doing setup with them (especially in the Cisco universe), and the BIRD documentation has absolutely zero info on doing any of it right now. Any information is only embedded in the source code. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Feb. 17, 2017

Re: BGP Large Communities

by Mike Horwath

On Fri, Feb 17, 2017 at 12:37:05AM -0600, David Farmer wrote: > BIRD 1.6.3 support it, so I'd like to suggest we think about a third route > server for testing with BGP Large Communities. If that goes well then > phase it in with the production servers maybe toward the end of 2017 when > more of the implementations for big iron routers make it in to production > code, > > What do others think? Quick view: I don't see why upgrading to 1.6.3 and turning it on for just folks wanting it could be done - just don't pass them onto other users. Unless I missed something. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Feb. 17, 2017

BGP Large Communities

by David Farmer

The RFC for BGP Large Communities has just been published; https://tools.ietf.org/html/rfc8092 There is also a draft discussing their use; https://tools.ietf.org/html/draft-ietf-grow-large-communities-usage-02 There are more details on the BGP Large Communities work and an implementation tracker at; http://largebgpcommunities.net/ BIRD 1.6.3 support it, so I'd like to suggest we think about a third route server for testing with BGP Large Communities. If that goes well then phase it in with the production servers maybe toward the end of 2017 when more of the implementations for big iron routers make it in to production code, What do others think? -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 <(612)%20626-0815> Minneapolis, MN 55414-3029 Cell: 612-812-9952 <(612)%20812-9952> ===============================================

Feb. 17, 2017

Re: Please welcome Limelight Networks to MICE!

by Kayla Olsen

Welcome, Limelight! Please provide contact information for your accounts payable team. Thank you! *Kayla Olsen* Senior Manager of Finance and Operations Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 612.877.6500 Office 320.894.3125 Mobile kolsen(a)neutralpath.net <kpowers(a)neutralpath.net> www.neutralpath.com Twitter: @NeutralPath [image: logo] *Please note my new name and email address: kolsen(a)neutralpath.net <kolsen(a)neutralpath.net> * On Mon, Feb 6, 2017 at 12:57 PM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > On Mon, Feb 06, 2017 at 09:25:13AM -0600, Jason Hanke wrote: > > Name: Limelight Networks > > ASN: 22822 > > IPv4: 206.108.255.43/24 > > IPv6: 2001:504:27:0:0:5926::1/64 > > Port: Main Switch xe-2/0/1 (Single Member LAG) > > Contact: peering-team(a)llnw.com > > BFD: NO > > Route Server: NO > > > > Limelight will upgrade to 2x10G LAG as soon as the new switch is > available. > > Okay, route servers setup to talk to them, and ae16.0 has been created on > core-sw1 > to bind xe-2/0/1 into a LAG running LACP for when they are ready in the > future. > > Welcome! > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades >

Feb. 14, 2017

Current Consolidated Contact

by Jason Hanke

Could the current Consolidated MICE contact reach out to me off list? -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Feb. 11, 2017

Re: Additional Google Ports

by Doug McIntyre

On Fri, Feb 10, 2017 at 02:17:15PM -0600, Jason Hanke wrote: > Please allocate the following ports to Google. They can be added to > the existing LAG. > > xe-2/0/29 > xe-0/1/3 > > Google will move to 100G as soon as it is available. Okay, two more links added onto LAG AE4 for whenever they have optics and are ready to plugin. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Feb. 10, 2017