- mice-discuss - lists.micemn.net

Role email accounts on the list
by Mike Horwath Sept. 28, 2018

Sept. 28, 2018

How do people feel about this? We just had someone join the list using a noc@ email address. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

3 2

Fwd: route server IRR objects: RIPE use for ARIN addresses deprecated, ARIN IRR & RPKI tutorials
by Richard Laager Sept. 25, 2018

Sept. 25, 2018

This is from the SeattleIX announce list. I'm forwarding it, with Chris's permission, in case this is relevant to anyone here. -------- Forwarded Message -------- Subject: route server IRR objects: RIPE use for ARIN addresses deprecated, ARIN IRR & RPKI tutorials Date: Tue, 25 Sep 2018 22:22:14 +0000 (UTC) From: Chris Caputo <ccaputo(a)seattleix.net> To: announce(a)seattleix.net tl;dr: - RIPE made changes which don't break anything now, but may in future. - I recommend you move your IRR records to the RIR which assigned or allocated your prefixes. - link to ARIN RPKI tutorial at bottom. Many of you that used RIPE to create your Internet Routing Registry (IRR) objects received an email from RIPE at the beginning of September about a change in their registry in which non-RIPE prefixes are now labeled with "source: RIPE-NONAUTH". This is part of an effort to improve the quality of IRR data for the purposes of reducing accidental or fraudulent BGP announcements. The idea being that the Regional Internet Registries (RIRs) know best who addresses have been assigned/allocated to. If you have your records at RIPE (or elsewhere and want to move to ARIN), I recommend you do the following: (note the example with my AS6456 will soon no longer work because I will be deleting my records at RIPE since they have been moved to ARIN) - First, determine your maintainer object name. This can be figured out by going to http://www.radb.net/query/ and running a query on your ASN or prefixes. For example, a query on my AS6456 reveals a RIPE maintainer "mnt-by" field "MAINT-ALTOPIA-RIPE". You may find you have multiple maintainers and multiple IRRs. Focus on the RIPE one if that is what you want to move. aut-num: AS6456 [...] mnt-by: MAINT-ALTOPIA-RIPE source: RIPE-NONAUTH - Using my "MAINT-ALTOPIA-RIPE" I can do an inverse query at RIPE to see all of my objects: $ whois -h whois.ripe.net -i mnt-by -B MAINT-ALTOPIA-RIPE aut-num: AS6456 as-name: ALTOPIA-6456 descr: Altopia AS 6456 [...] as-set: AS-ALTOPIA descr: Altopia Corporation members: AS6456 [...] route: 208.90.168.0/22 descr: ALTOPIA-V4-1 assigned by ARIN origin: AS6456 [...] route6: 2620:0:cf0::/48 descr: ALTOPIA-V6-1 assigned by ARIN origin: AS6456 [...] etc... - Save a copy of all of your objects so you can use the result to aide in your move to ARIN. - Refer to https://www.seattleix.net/irr-tutorial#arin for a new tutorial on how to get set up at ARIN's IRR. - Use http://irrexplorer.nlnog.net to visualize which IRRs are reporting your prefixes or ASN. - After all of your ARIN objects are moved to ARIN, work to delete your ARIN objects at RIPE or elsewhere as part of being tidy. Bonus! I also made an ARIN Resource Public Key Infrastructure (RPKI) tutorial. Turns out RPKI is pretty easy to configure, with respect to making it so your own ARIN prefixes are somewhat (*) protected from being announced by unauthorized ASNs. (*: with respect to networks running RPKI validators) - https://www.seattleix.net/irr-tutorial#arinrpki Feedback & corrections welcome! Chris

2 1

Arista Test Drive Training Wednesday, October 3rd
by John McLaughlin Sept. 23, 2018

Sept. 23, 2018

Hello MICE Members: If you can join us for a day of free training please use the links below to register and review what an Arista Test Drive covers. https://solutions.arista.com/2018-09-atd-minnetonka-mn <https://solutions.arista.com/2018-09-atd-minnetonka-mn> https://solutions.arista.com/atd-training <https://solutions.arista.com/atd-training> ATD TRAINING What we offer: A curriculum designed to deliver world-class content and learning experience Small, intimate class sizes, led by our local engineers, for greater classroom interaction In addition to the schedule listed, we can add classes to fit your needs. Just tell us when and where, and we take care of the rest Please reach out to your Arista Account Manager or Training(a)Arista.com <mailto:Training@Arista.com> for more information! Thanks, -JMc John McLaughlin North Central Sales jmclaughlin(a)arista.com Cell# 612-816-9024 https://www.barrons.com/articles/worlds-best-ceos-growth-leaders-1527304583…

1 0

Power a pdu?
by Ryan Goldberg Sept. 15, 2018

Sept. 15, 2018

Anyone at 511 and have 208v pdu with L6-30 in and a few c13 and c19 out? Ran into a sticky spot and could use one or two tonight. Can order and ship new to you or return in 2.5 weeks. Sorry for the OT, slap my hand if necessary. Ryan 218-390-5485

2 3

MICE Mailing Address
by Kayla Olsen Sept. 10, 2018

Sept. 10, 2018

*This is a duplicate notice for some of you, please disregard if it's old news...* Greetings, The mailing address for MICE (Midwest Internet Cooperative Exchange) has changed. Please update your records to: Midwest Internet Cooperative Exchange PO Box 153 Mankato MN 56002-0153 http://micemn.net/ Thank you, Kayla Olsen MICE Treasurer

1 0

Routing of non-IX traffic
by Frank Bulk Aug. 23, 2018

Aug. 23, 2018

When I force a traceroute to originate from our MICE-facing connection, the first hop is 206.108.255.50 (AS32609 aka CNS). Any reason why? To making things more interesting, Incapsula-destined traffic goes via Paul Bunyan. Here's just one example: traceroute to www.yamaha-dealers.com (45.60.73.16), 30 hops max, 60 byte packets 1 AS32609.micemn.net (206.108.255.50) 14.059 ms 14.084 ms 14.076 ms 2 cns70.cnsllc.net (205.149.150.9) 18.484 ms 18.434 ms 18.507 ms 3 fg30.ips.cnsllc.net (205.149.150.30) 20.254 ms 20.346 ms 20.267 ms 4 crss2.PaulBunyan.net (205.149.159.197) 20.527 ms 20.562 ms 20.619 ms 5 cra.PaulBunyan.net (205.149.159.181) 23.398 ms fp233.ips.PaulBunyan.net (205.149.159.233) 22.669 ms cra.PaulBunyan.net (205.149.159.181) 23.393 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * SiouxCenter-Arista-North(s1) The reason I stumbled across this is because we've had more than a dozen customers over the last month complain about access to Incapsula-protected sites. Packet captures show TCP RSTs coming from the far side. Regards, Frank Bulk AS53347

11 18

Direct peering to Yahoo! unstable over the last few days
by Frank Bulk Aug. 20, 2018

Aug. 20, 2018

Anyone else seeing the same as us? Aug 17 17:55:10 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.58 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:10 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 17 17:55:14 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.59 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:14 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 17 17:55:17 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 2001:504:27::2846:0:2 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:17 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 17 18:02:13 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 18:02:19 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 18:02:48 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:30:59 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:31:03 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:31:06 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:38:05 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:38:12 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:38:20 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 00:54:55 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 00:54:57 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 00:54:59 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 01:02:41 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 01:02:49 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 01:02:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:01:30 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:01:32 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:01:35 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:15:55 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:16:00 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:16:00 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:36:50 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:36:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:36:56 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:47:17 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:47:21 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:47:24 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established

3 3

Compudyne (AS47096) Network Maintenance
by Ryan Nelson Aug. 14, 2018

Aug. 14, 2018

We will be migrating our MICE connection to a new router tomorrow. In preparation for this we will be shutting down all BGP sessions in the early AM and intend to have them back online by early evening. Thanks, and sorry for the short notice, Ryan Nelson | Network Infrastructure Architect Compudyne | 306 W Michigan Street - Suite 200 | Duluth, MN 55802 rnelson(a)compudyne.com<mailto:rnelson@compudyne.com> | 218.336.2220 | compudyne.com<http://www.compudyne.com/> Duluth | Hibbing | Saint Paul | Marquette | Houghton | Anchorage ________________________________ [cid:image002.png@01D0BA36.584BB020]

1 0

Facebook/Instagram
by AnthonyAnderberg＠nuvera.net Aug. 9, 2018

Aug. 9, 2018

Has anyone else gotten reports of issues with Facebook/Instagram the last day or two? We're seeing intermittent problems where Facebook pages will load normally but then some of the pictures/videos in the page will be slow loading. I haven't really narrowed it beyond a handful of source addresses in Facebook's network, mostly in the 157.240.2.0/24 range, and haven't seen any other service issues or narrowed it to any one upstream carrier. It doesn't appear any of the content is coming through MICE, but I'm curious if anyone is/has seen something similar. We've reached out to Facebook but haven't gotten a response yet. Thanks in advance, anthony [Anthony_Anderberg]<https://www.nuvera.net/>

2 1

Re: Please welcome Global Net to MICE!
by Richard Laager Aug. 1, 2018

Aug. 1, 2018

On 07/30/2018 02:32 PM, Jay Hanke wrote: > Route Server: No I communicated with Global Net off-list. This is actually a "Yes" now. They _do_ want to be setup on the route servers. -- Richard

2 1

UG 29 Election
by Richard Laager Aug. 1, 2018

Aug. 1, 2018

At UG 29 in October, we will be holding an election for a board seat. The board consists of three seats with staggered terms, such that one seat comes up for re-election each year (at the fall meeting). This year, Reid's seat is up for election. Reid _is_ running for re-election. If anyone else is interested in running, please nominate yourself. Voting will be done in person. If you will not be attending in person, you must designate a proxy, in advance, in writing. The bylaws state that you send that to the Chief Manager (me, Richard Laager), and electronic means are acceptable. So a simple email is sufficient. If you are having trouble finding a proxy who will be there in person, ask on the list or I can help you find someone. -- Richard

1 0

Please welcome Global Net to MICE!
by Jay Hanke July 30, 2018

July 30, 2018

Name: Global Net Port: Ethernet5/37 (Main Switch) Speed: 10G ASN: 395466 IPv4: 206.108.255.97/24 IPv6: 2001:504:27:0:6:08ca::1/64 Route Server: No BFD Support: No Peering Contact: peering(a)theglobal.net Please provide your Arista compatible optic to Cologix or a member of the tech committee. Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

1 0

MICE BFD Settings
by AnthonyAnderberg＠nuvera.net July 25, 2018

July 25, 2018

At the last UG meeting it was suggested that we document MICE's route server BFD settings, that is done now: http://www.micemn.net/technical.html Was good seeing everyone again, anthony [Anthony_Anderberg]<https://www.nuvera.net/>

1 0

Dyn blog post has some recommendations for IXPs who may experience bad actors
by Frank Bulk July 12, 2018

July 12, 2018

The whole blog post I interesting, but the last fifth relates to IXPs: https://dyn.com/blog/shutting-down-the-bgp-hijack-factory/ Food for thought. Frank

1 0

Not learning all routes from RR#2
by Frank Bulk June 27, 2018

June 27, 2018

We (AS53347) moved to a new border router overnight and had some issues with getting our MICE route reflector peerings up -- we'd learn a route or two per second. We had to tweak our Arista's BGP configuration to not "enforce-first-as". Most other direct peers were fine. Eventually RR #1 came up just fine, but RR #2 continues to languish, learning just learning about 10,900 routes. SiouxCenter-Arista-North(s1)#show ip bgp sum BGP summary information for VRF default Router identifier 207.32.15.22, local AS number 18883 Neighbor Status Codes: m - Under maintenance Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State PfxRcd PfxAcc 206.108.255.1 4 53679 44493 4138 0 0 10:56:46 Estab 56188 56188 206.108.255.2 4 53679 39124 7640 0 0 11:38:40 Estab 10929 10929 I'm not sure if we have remote access to the RR's, but whoever does, any hints as to why we're experiencing this behavior? Frank

4 4

Please welcome Muscatine Power and Water to MICE
by Jeremy Lumby June 22, 2018

June 22, 2018

Name: Muscatine Power and Water Port: MN VoIP Remote - E7 ASN: 33734 IPv4: 206.108.255.96/24 IPv6: 2001:504:27:0:0:83c6::1/64 BFD: Yes Route Server: Yes Peering Contact Email: dominickl(a)mpw.org Thanks, Jeremy Lumby Minnesota VoIP 9217 17th Ave S Suite 216 Bloomington, MN 55425 Main: 612-355-7740 x211 Direct: 612-392-6814 EFax: 952-873-7425 jlumby(a)mnvoip.com

2 1

Please welcome Wholesale Internet to MICE!
by Jay Hanke June 19, 2018

June 19, 2018

Name: Wholesale Internet Port: MN VoIP Remote ASN: 32097 IPv4: 206.108.255.95/24 IPv6: 2001:504:27:0:0:7d61::1/64 BFD: No Route Server: Yes Peering Contact Email: noc(a)wholesaleinternet.net Jeremy, can you update with a port when you get a chance? Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

3 2

Please welcome BankOnIT to MICE!
by Jay Hanke June 19, 2018

June 19, 2018

Name: BankOnIT, LLC Port: TBD (MN VoIP Remote) ASN: 46416 IPv4: 206.108.255.94 /24 IPv6: 2001:504:27:0:0:b550::1 /64 BFD Support: No Route Server: Yes Peering Contact Email: peering(a)bankonitusa.com Jeremy, Please confirm the port assignment on your switch. Welcome Aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

3 2

email scrapers - update participants list?
by Andrew Hoyos June 14, 2018

June 14, 2018

Hiya folks, Looks like we’ve been getting a small volume of spam based on seemingly culled email addresses from the MICE Participants list, located here: https://www.micemn.net/participants.html <https://www.micemn.net/participants.html> Any thoughts on obfuscating the email addresses listed there with a (at) and (dot) to help prevent? Or perhaps some other clickable CSS/Javascript thing that accomplishes the same? Or, perhaps the minimal amount of spam is worth the convenience of clicking… Thoughts? — Andrew Hoyos hoyosa(a)gmail.com

2 1

US Inernet Network Maintenance
by Justin Krejci June 14, 2018

June 14, 2018

Hello, US Internet will be rebooting the router connected to MICE next week to apply OS updates. We will shutdown all BGP sessions in advance to allow traffic to re-route. This will happen sometime on the June 19th overnight into June 20th. The precise timing is unknown as this is just one of numerous other network changes occurring that night. Duration of impact should be less than 30 minutes. Thanks! Justin

1 0

Please welcome Pavlov Media to MICE!
by Jay Hanke June 8, 2018

June 8, 2018

Name: Pavlov Media Port: Ethernet4/24 (Main Switch) ASN: 23473 IPv4: 206.108.255.93 /24 IPv6: 2001:504:27:0:0:5bb1::1 /64 Route Server: Yes BFD: NO Peering Contact: peering(a)pavlovmedia.net Please provide you 10G Arista compatible SFP+ when you order your cross connect. We will post the port assignment information to the MICE website. The public posting (or this email) will serve as your LOA/CFA. Welcome aboard -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io

2 1

Amazon Port Augment
by Jay Hanke June 7, 2018

June 7, 2018

Amazon is adding additional ports and a redundant LAG. New Physical ports (LAG 23): Ethernet4/23 (10g) Ethernet5/23 (10g) New IP Addresses are: 206.108.255.112/24 2001:504:27:0:0:407d::2/64 Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io

1 0

Changing hats
by Frank Bulk June 1, 2018

June 1, 2018

My $DAYJOB employer, Premier Communications (AS53347) is planning to move our interconnection with MICE to FiberNet (AS18883). I'm the technical contact for both. Can we get another IX IP to accomplish this transition? Organizationally, what, if anything, do I need to do with MICE? I know that I will need to make changes with all our direct peers, too. So I would need both IPs for a while. Regards, Frank

2 1

RFC: Remote Switch in Duluth
by Richard Laager May 31, 2018

May 31, 2018

The following is from Ryan Goldberg of Compudyne: ---- Compudyne/AS47096 is interested in operating a MICE remote switch in Duluth. We have two 10G paths from 511 to Duluth (one on Charter, one on Enventis) in a ring of 5 Juniper MX boxes (2 at 511, 3 in Duluth – the 3 in Duluth are interconnected over dark fiber). We hit a little over 5G on 5min averages in total between the two 511<->Duluth legs. Latency is 4-5ms. We currently participate in MICE via MNVoip’s extension, mainly because it makes more overall sense to pick up MICE + SIX + Denver + KC all on one interface (for now). We’d probable leave it like that for a while. For the proposed extension switch we’d do a two site VPLS config on the MXes, with on a fresh, dedicated 10gig port at 511 and corresponding 10gig port in Duluth. We’d start with an EX4200-24F in Duluth, and run the usual Juniper-y stuff (from http://micemn.net/technical.html) Initial participants would only be on 1gig ports on the 4200. As for location, we’re currently leaning toward “the Missabe Building” at 227 W 1st St, Duluth, MN – this is our primary downtown Duluth POP, and aside from our fiber, and there’s high-count fiber from at least 5 other carriers in the building. The space has dual AC and is backed by generator power. Upgrade path is 100G 511<->Duluth, at least on one leg. If business drives it, we’ll just do it. Otherwise it’s budgeted for next year. As for the switch, we’d move to a ex4550. ---- Without taking any position on this here yet, I'd like to highlight a couple of facts: The proposed transport is over a VPLS link (i.e. shared with other traffic, not a dedicated wave). In the past, and quite possibly still, we have had participants connected over shared links, but not entire remote switches. -- Richard

3 2

Neutral Path link issue between Belle Plaine and MICE
by Frank Bulk May 5, 2018

May 5, 2018

I woke up this morning to see emails about our BGP sessions with MICE to be down. Look at alarms and graphs I see that the link from Belle Plaine to MICE is down since about 12:39 am. According to the NeutralPath NOC (operated by WINS?), something about how a temporary fiber fix for emergency fiber work failed? I wasn't even aware of any emergency fiber work. The NOC said that a tech was dispatched and he was hoping they would be able to fix it in the next few hours. Frank

5 9