- mice-discuss - lists.micemn.net

Re: Looking glass

by Doug McIntyre

On Fri, Nov 03, 2017 at 11:01:49AM -0500, Andrew Hoyos wrote: >Does MICE itself have general use transit available for website, OOB, graphing servers, etc, where this LG (or at least 1 leg of it) could live instead? ipHouse has donated some transit for MICE use in the past. It can still keep doing that if this is desired to be moved to a transitable IP address. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Nov. 3, 2017

Re: Looking glass

by Steve Howard

Nov. 3, 2017

Re: Looking glass

by Andrew Hoyos

Yeah, that seems like a bad idea. Generally speaking, folks should never really be carrying the MICE /24 in their IGP’s anyway. It’s a bad idea, and can be harmful. Not carrying it (and using next-hop-self) protects both you and MICE. The IXP prefix shouldn’t, in theory, really be reachable from any device not directly connected in to that /24. Does MICE itself have general use transit available for website, OOB, graphing servers, etc, where this LG (or at least 1 leg of it) could live instead? -- Andrew Hoyos hoyosa(a)gmail.com > On Nov 3, 2017, at 10:30 AM, Steve Howard <showard(a)paulbunyan.net> wrote: > > Note that the IP address for the Looking Glass is within the MICE IP space and probably does not have connectivity to the global internet. Perhaps something to look at in the future? > > > On 11/03/2017 07:39 AM, Doug McIntyre wrote: >> On Fri, Nov 03, 2017 at 09:15:09AM +0000, Frank Bulk wrote: >>> Is the MICE Looking Glass down? When I telnet or SSH to it, I get no prompt. >> >> Hmm, doesn't seem to be. Works for me. (both ssh & telnet). >> Which hostname are you using? >> >> $ ssh rviews(a)lg.micemn.net C >> >> ********************************************************************** >> >> >> >> MICE MN BGP Route Views >> >> http://www.micemn.net/ >> >> >> >> This router has views of the full routing table from the route reflectors >> >> of the MICEMN peering point in Minneapolis, MN, USA. >> The list of participants are located at http://www.micemn.net/participants.html >> >> >> >> Login with username 'rviews' to access the router via telnet/ssh. >> ********************************************************************** >> >> >> >> >> >> >> micemn-lg>show ip route >> Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP >> D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 >> E1 - OSPF external type 1, E2 - OSPF external type 2 >> i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 >> ia - IS-IS inter area, * - candidate default, U - per-user static route >> o - ODR, P - periodic downloaded static route >> >> Gateway of last resort is 216.250.183.14 to network 0.0.0.0 >> >> B 204.221.17.0/24 [20/25] via 206.108.255.121, 2d20h >> B 203.221.22.0/24 [20/474] via 206.108.255.52, 3w1d >> B 192.170.106.0/24 [20/474] via 206.108.255.52, 7w0d >> B 199.16.214.0/24 [20/95] via 206.108.255.52, 2w0d >> B 194.50.241.0/24 [20/1265] via 206.108.255.52, 5d19h >> B 202.70.142.0/24 [20/474] via 206.108.255.52, 3w1d >> B 202.49.249.0/24 [20/260] via 206.108.255.52, 7w0d >> B 196.223.25.0/24 [20/960] via 206.108.255.52, 1d23h >> B 203.18.218.0/24 [20/474] via 206.108.255.52, 3w1d >> B 202.154.83.0/24 [20/474] via 206.108.255.52, 7w0d >> B 203.190.112.0/24 [20/1970] via 206.108.255.52, 1d07h >> B 199.5.199.0/24 [20/90] via 206.108.255.52, 3w1d >> B 208.66.148.0/24 [20/308] via 206.108.255.52, 5w3d >> B 203.142.67.0/24 [20/1970] via 206.108.255.52, 17:42:42 >> B 199.96.161.0/24 [20/265] via 206.108.255.52, 1d14h >> B 192.189.123.0/24 [20/81] via 206.108.255.52, 4w3d >> B 192.83.149.0/24 [20/482] via 206.108.255.52, 2w3d >> >> ... >> >> >> > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Nov. 3, 2017

Re: Looking glass

by Steve Howard

Nov. 3, 2017

Re: Looking glass

by Doug McIntyre

On Fri, Nov 03, 2017 at 09:15:09AM +0000, Frank Bulk wrote: >Is the MICE Looking Glass down? When I telnet or SSH to it, I get no prompt. Hmm, doesn't seem to be. Works for me. (both ssh & telnet). Which hostname are you using? $ ssh rviews(a)lg.micemn.net C ********************************************************************** MICE MN BGP Route Views http://www.micemn.net/ This router has views of the full routing table from the route reflectors of the MICEMN peering point in Minneapolis, MN, USA. The list of participants are located at http://www.micemn.net/participants.html Login with username 'rviews' to access the router via telnet/ssh. ********************************************************************** micemn-lg>show ip route Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route Gateway of last resort is 216.250.183.14 to network 0.0.0.0 B 204.221.17.0/24 [20/25] via 206.108.255.121, 2d20h B 203.221.22.0/24 [20/474] via 206.108.255.52, 3w1d B 192.170.106.0/24 [20/474] via 206.108.255.52, 7w0d B 199.16.214.0/24 [20/95] via 206.108.255.52, 2w0d B 194.50.241.0/24 [20/1265] via 206.108.255.52, 5d19h B 202.70.142.0/24 [20/474] via 206.108.255.52, 3w1d B 202.49.249.0/24 [20/260] via 206.108.255.52, 7w0d B 196.223.25.0/24 [20/960] via 206.108.255.52, 1d23h B 203.18.218.0/24 [20/474] via 206.108.255.52, 3w1d B 202.154.83.0/24 [20/474] via 206.108.255.52, 7w0d B 203.190.112.0/24 [20/1970] via 206.108.255.52, 1d07h B 199.5.199.0/24 [20/90] via 206.108.255.52, 3w1d B 208.66.148.0/24 [20/308] via 206.108.255.52, 5w3d B 203.142.67.0/24 [20/1970] via 206.108.255.52, 17:42:42 B 199.96.161.0/24 [20/265] via 206.108.255.52, 1d14h B 192.189.123.0/24 [20/81] via 206.108.255.52, 4w3d B 192.83.149.0/24 [20/482] via 206.108.255.52, 2w3d ... -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Nov. 3, 2017

Looking glass

by Frank Bulk

Is the MICE Looking Glass down? When I telnet or SSH to it, I get no prompt. Kind regards, Frank

Nov. 3, 2017

Re: MICE UG 25 Meeting

by Richard Laager

The (draft) UG 25 minutes are available at the usual place: http://micemn.net/resources.html Direct link: http://micemn.net/files/MICE%20UG%2025%20-%20Minutes.pdf Thanks to Mike Johnston for taking minutes! -- Richard

Nov. 1, 2017

Re: Graph Updates

by Richard Laager

On 10/30/2017 12:39 PM, anthonyanderberg(a)nu-telecom.net wrote: > I’ve been watching the Aggregate Ingress/Egress graph values diverge > with increasing discomfort and finally had a couple free hours to look > into it yesterday and found the combination of the last round of CDN LAG > upgrades and cruft left over from migrating from the old Juniper core > was causing the Ingress values to skew high. In the end it was easier > to just create a new Aggregate graph so I’ve done that and will remove > the old graph once the web site is updated: > > http://micelg.usinternet.com/export/graph_1430.html Thanks for looking into this. I have updated the website. -- Richard

Oct. 30, 2017

Graph Updates

by anthonyanderberg＠nu-telecom.net

I've been watching the Aggregate Ingress/Egress graph values diverge with increasing discomfort and finally had a couple free hours to look into it yesterday and found the combination of the last round of CDN LAG upgrades and cruft left over from migrating from the old Juniper core was causing the Ingress values to skew high. In the end it was easier to just create a new Aggregate graph so I've done that and will remove the old graph once the web site is updated: http://micelg.usinternet.com/export/graph_1430.html I also took the time to dig into the IP4/6 Peer/Prefix graphs and think I've got them (mostly) fixed now too, they're under the "Route Server" menu item in Cacti. Thanks for everyone's suggestions on that topic. As always let me know if anything seems wrong or silly. Cheers, anthony Anthony Anderberg Sr. Systems Analyst [NUtel_email_logo_1] 320-234-5239 anthonyanderberg(a)nu-telecom.net<mailto:anthonyanderberg@nu-telecom.net> www.nutelecom.net<http://www.nutelecom.net>

Oct. 30, 2017

Re: Multi-IX Traffic Management?

by Michael Hare

We (AS 3128) are mostly a Juniper shop. There are situations where our longhaul is not redundant and less diverse than you would hope. It is a problem easily solved with $$. At times this unfortunate situation leaves us with several hundred thousand routes to converge; it takes time. We're looking at JunOS 16 for deployment this winter. In addition to RPD being slightly threaded, JunOS 16.1 has features to optimize the order of processing RIB changes (policy-statement based). Our challenge becomes defining priority, optimizing on bandwidth per AS/subnet doesn't necessarily tell the whole story, some low bandwidth things (DNS) are paramount [and thankfully rather static]. For now we also have our internet tables in global unicast table. JunOS currently has features that allow you to program a secondary forwarding next hop but it is reserved for l3vpns. Doing that for the global unicast table is an uncommitted ER. I haven't yet started to seriously explore putting the internet in a VRF. -Michael >>-----Original Message----- >>From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf >>Of Jason Hanke >>Sent: Monday, October 30, 2017 9:01 AM >>To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >>Subject: Re: [MICE-DISCUSS] Multi-IX Traffic Management? >> >>As a transport seller, We're seeing most networks most commonly buy >>linear paths to two or more IXes. Typically going opposite directions >>from their home base. We're also starting to see smaller operators >>exclusively doing remote peering. A typical set up is buying identical >>transport to the 2 adjacent IX buildings. >> >>On wavelengths, the link failure can be passed back to from end to >>end. Granted, a long-haul wavelength isn't as stable as a cross >>connect. >> >>If a network doesn't have any remote gear the convergence is governed >>by EBGP vs IBGP/IGP if there is an additional router. For remote >>setups, in particular with Ethernet transport we're seeing more and >>more BFD on the sessions. >> >>Jay >> >>On Mon, Oct 30, 2017 at 8:27 AM, Michael Hare <michael.hare(a)wisc.edu> >>wrote: >>> For those buying wavelengths (compared to an mpls circuit), are you >>buying diverse transport? If not, how are you dealing with convergence >>stability? >>> >>> -Michael >>> >>>>>-----Original Message----- >>>>>From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On >>Behalf >>>>>Of Colin Baker >>>>>Sent: Friday, October 27, 2017 3:29 PM >>>>>To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >>>>>Subject: Re: [MICE-DISCUSS] Multi-IX Traffic Management? >>>>> >>>>>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 >> >> >> >>-- >>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. 30, 2017

Re: Multi-IX Traffic Management?

by Jason Hanke

As a transport seller, We're seeing most networks most commonly buy linear paths to two or more IXes. Typically going opposite directions from their home base. We're also starting to see smaller operators exclusively doing remote peering. A typical set up is buying identical transport to the 2 adjacent IX buildings. On wavelengths, the link failure can be passed back to from end to end. Granted, a long-haul wavelength isn't as stable as a cross connect. If a network doesn't have any remote gear the convergence is governed by EBGP vs IBGP/IGP if there is an additional router. For remote setups, in particular with Ethernet transport we're seeing more and more BFD on the sessions. Jay On Mon, Oct 30, 2017 at 8:27 AM, Michael Hare <michael.hare(a)wisc.edu> wrote: > For those buying wavelengths (compared to an mpls circuit), are you buying diverse transport? If not, how are you dealing with convergence stability? > > -Michael > >>>-----Original Message----- >>>From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf >>>Of Colin Baker >>>Sent: Friday, October 27, 2017 3:29 PM >>>To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >>>Subject: Re: [MICE-DISCUSS] Multi-IX Traffic Management? >>> >>>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 -- 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. 30, 2017

Re: Multi-IX Traffic Management?

by Jeremy Lumby

-----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Michael Hare Sent: Monday, October 30, 2017 8:27 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Multi-IX Traffic Management? For those buying wavelengths (compared to an mpls circuit), are you buying diverse transport? If not, how are you dealing with convergence stability? -Michael >>-----Original Message----- >>From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf >>Of Colin Baker >>Sent: Friday, October 27, 2017 3:29 PM >>To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >>Subject: Re: [MICE-DISCUSS] Multi-IX Traffic Management? >> >>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. 30, 2017

Re: Multi-IX Traffic Management?

by Michael Hare

For those buying wavelengths (compared to an mpls circuit), are you buying diverse transport? If not, how are you dealing with convergence stability? -Michael >>-----Original Message----- >>From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf >>Of Colin Baker >>Sent: Friday, October 27, 2017 3:29 PM >>To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >>Subject: Re: [MICE-DISCUSS] Multi-IX Traffic Management? >> >>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. 30, 2017

Re: Multi-IX Traffic Management?

by Richard Laager

I peer at SIX only with networks that I can't peer with at MICE. If a network is at both, I filter out their routes from SIX's route server and I ask the SIX route server to not propagate my routes to them (using the relevant communities). -- Richard

Oct. 27, 2017

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

Re: Please Welcome Country Wireless to MICE

by Doug McIntyre

On Thu, Oct 05, 2017 at 11:17:17AM -0500, Jason Hanke wrote: >Company Name: Country Wireless >ASN: 16616 >IPv4: 206.108.255.88/24 <http://206.108.255.28/24> >IPv6: 2001:504:27:0:0:1f9f::1/64 >Route Server Connection (yes/no): yes >BFD Support (yes/no): No >Peering Contact Email address: support(a)countrywireless.com >Remote port assignment number: Main Switch Ethernet 5/16 After a little delay, this is all set in the route servers. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 11, 2017