- mice-discuss - lists.micemn.net

Re: Multi-IX Traffic Management?

by Jeremy Lumby

Matthew, My few cents on your questions: Since there are extension switches for some of these other IXes in Minneapolis, often times the cost is far less than the wavelength, a term contract is not even needed, and by having multiple people sharing the cost of an extension, sometimes it can cover the cost of diverse waves (I have been surprised at how often a wave will go down, when you have thousands of miles of fiber, a lot can go wrong) I personally use prepends, and MEDs to manipulate traffic paths. Many of the CDNs have complicated algorithms that go far beyond BGP, and factor in things like load on the cache, geo-location of the IP, and latency. As for the Chicago problem, I still see my upstreams all trying to take me there. This gives me an option to go the other direction. After the diverse content, the second reason I peer at other exchanges is I have a direct relationship with the peer, so I cutout the delays/red tape of working with an upstream to resolve the issue. Not to mention I can avoid if the upstream gets into a pissing match about who they will/won't peer with, and it causes their links to saturate. Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Matthew Beckwell Sent: Friday, October 27, 2017 3:02 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Multi-IX Traffic Management? For my own curiosity: I've seen quite a few networks in the last year or so connecting themselves to other out-of-market IX's (I presume getting some cheap wavelengths and bringing it back to Minnesota). A couple of questions for those of you that are doing this: 1. I'm assuming this is enabling you to accommodate requirements from other networks that require peering at multiple locations, even though technically your network doesn't really extend that far (or maybe it's something else?). 2. How are folks monitoring, managing, or manipulating this out-of-market traffic? (Using BGP MED, Prepending, Localpref, or some other mechanism to "prefer" your traffic enter and exit closer to where you really are?) I've seen some funny business with these kinds of network arrangements. Google DNS responses coming from SIX......CloudFlare cache response coming from Omaha IX. It seems like it's "the Chicago problem" (that MICE was founded to avoid) all over again-- except this time around we're doing it with private links all over the country instead of public transit? Just curious what people have found to be best practices with this type of arrangement. ~Matthew To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Oct. 27, 2017

Re: Multi-IX Traffic Management?

by Colin Baker

On 27.10.2017 15:01, Matthew Beckwell wrote: > For my own curiosity: > > I've seen quite a few networks in the last year or so connecting > themselves to other out-of-market IX's (I presume getting some cheap > wavelengths and bringing it back to Minnesota). > > A couple of questions for those of you that are doing this: > > 1. I'm assuming this is enabling you to accommodate requirements from > other networks that require peering at multiple locations, even though > technically your network doesn't really extend that far (or maybe it's > something else?). For us, the goal is to reach networks which are not on exchanges which we're already connected. The big ones are at MICE, but there are other exchanges we can get to reasonably inexpensively that have such a large number of networks connected that it makes sense financially (compared to buying more transit). Traffic from a huge number of ASNs, particularly if most are on a route server, can really add up. Peering in multiple locations is a nice benefit to this, but usually not a primary goal for us. > 2. How are folks monitoring, managing, or manipulating this > out-of-market traffic? (Using BGP MED, Prepending, Localpref, or some > other mechanism to "prefer" your traffic enter and exit closer to > where you really are?) If you haven't already, install as-stats (https://github.com/manuelkasper/AS-Stats) to monitor things, which will make it clear if something is out of whack. In most cases, our IGP handles outbound traffic in a way the makes sense. Inbound traffic can be trickier - a few networks will publish action communities or accept MEDs, and we utilize those tools when available. Prepending is occasionally useful. Announcing more specifics in certain spots always felt like a jerk move so I tend to avoid that, but that's a thing I suppose. -- Colin Baker SupraNet Communications, Inc. (608) 572-7634 colinb(a)supranet.net This message is subject to the SupraNet Email Confidentiality Policy which is located at http://supranet.net/confidentiality

Oct. 27, 2017

Re: Please Welcome Omni-Tech to MICE!

by Doug McIntyre

On Fri, Oct 27, 2017 at 02:40:19PM -0500, Jason Hanke wrote: >Company Name : Omni-Tech Inc. >ASN: 54821 >IPv4: 206.108.255.90/24 >IPv6: 2001:504:27:0:0:d625::1/64 >Port: Neutral Path Remote port ge-0/0/11 >BFD Support: NO >Route Servers: YES >Peering Contact email: peering(a)omni-tech.net > All set on the route servers for Omni-Tech, Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 27, 2017

Multi-IX Traffic Management?

by Matthew Beckwell

For my own curiosity: I've seen quite a few networks in the last year or so connecting themselves to other out-of-market IX's (I presume getting some cheap wavelengths and bringing it back to Minnesota). A couple of questions for those of you that are doing this: 1. I'm assuming this is enabling you to accommodate requirements from other networks that require peering at multiple locations, even though technically your network doesn't really extend that far (or maybe it's something else?). 2. How are folks monitoring, managing, or manipulating this out-of-market traffic? (Using BGP MED, Prepending, Localpref, or some other mechanism to "prefer" your traffic enter and exit closer to where you really are?) I've seen some funny business with these kinds of network arrangements. Google DNS responses coming from SIX......CloudFlare cache response coming from Omaha IX. It seems like it's "the Chicago problem" (that MICE was founded to avoid) all over again-- except this time around we're doing it with private links all over the country instead of public transit? Just curious what people have found to be best practices with this type of arrangement. ~Matthew

Oct. 27, 2017

Please Welcome Omni-Tech to MICE!

by Jason Hanke

Company Name : Omni-Tech Inc. ASN: 54821 IPv4: 206.108.255.90/24 IPv6: 2001:504:27:0:0:d625::1/64 Port: Neutral Path Remote port ge-0/0/11 BFD Support: NO Route Servers: YES Peering Contact email: peering(a)omni-tech.net Welcome Aboard! -- 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

Oct. 27, 2017

Re: 2018 Fees Update?

by Richard Laager

On 10/25/2017 01:35 PM, Jason Hanke wrote: > Has the board decided on 2018 fees? We seem to all be in agreement to leave the port fees at the same levels as 2017. -- Richard

Oct. 26, 2017

Re: Please Welcome MN Wifi to MICE!

by Doug McIntyre

On Wed, Oct 25, 2017 at 02:24:23PM -0500, Jason Hanke wrote: >Company Name: Minnesota WiFi >ASN: 393455 >IPv4: 206.108.255.89/24 >IPv6: 2001:504:27:0:6:00ef::1/64 >Peering Contact email: darin.steffl(a)mnwifi.com >Billing Email Address: darin.steffl(a)mnwifi.com >Billing Postal Address: PO Box 81, Kasson, MN 55944 >BFD Support (y/N) do you support BFD on your sessions? NO >Route Server Support (Y/n) do you want to use the MICE route servers? YES Okay, the route servers are all set and ready to go for them. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 25, 2017

Please Welcome MN Wifi to MICE!

by Jason Hanke

Company Name: Minnesota WiFi ASN: 393455 IPv4: 206.108.255.89/24 IPv6: 2001:504:27:0:6:00ef::1/64 Peering Contact email: darin.steffl(a)mnwifi.com Billing Email Address: darin.steffl(a)mnwifi.com Billing Postal Address: PO Box 81, Kasson, MN 55944 BFD Support (y/N) do you support BFD on your sessions? NO Route Server Support (Y/n) do you want to use the MICE route servers? YES Connecting via MN VoIP Remote Switch. Please update your PeeringDB connection as soon as your port is ready. Welcome Aboard! -- 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

Oct. 25, 2017

2018 Fees Update?

by Jason Hanke

Has the board decided on 2018 fees? -- 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

Oct. 25, 2017

MICE Pull up Display

by Jason Hanke

Does anyone know where the MICE pull up display is? -- 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

Oct. 16, 2017