- mice-discuss - lists.micemn.net

Nanog?
by Reid Fishler Sept. 30, 2018

Sept. 30, 2018

Whose coming? This week, Vancouver. Reid -- Reid Fishler Director Hurricane Electric +1-510-580-4178

2 1

Re: South Front Networks, LLC Remote switch request
by Richard Laager Sept. 28, 2018

Sept. 28, 2018

I'm bringing this remote switch request to the discussion list per our remote switch policy: http://micemn.net/technical.html On 09/28/2018 09:25 AM, Jay Hanke wrote: > South Front Networks requests approval to install a MICE Remote Switch > in SFN's Albert Lea Datacenter. > > South Front proposes the following: > 1) SFN will acquire a Juniper QFX5100 or Arista comparable switch > dedicated to MICE. > 2) SFN will acquire and pay for any required connectivity back to the > MN VoIP remote switch, MN VoIP and SFN remote switches will share the > existing 40 Gbps MICE link into the main fabric. Both SFN and MN VoIP > agree to upgrade capacity as needed on the uplink to the main switch. > 3) SFN will initially install 20 Gbps of capacity and will upgrade > capacity as needed per the board and technical committee requirements > 4) SFN agrees to enforce the MICE technical port rules > 5) SFN agrees to coordinate connections to the new remote switch > 6) SFN agrees to inform all prospective members that connections going > to the SFN MICE Remote switch are not connected directly to MICE. > 7) SFN agrees to perform any required configuration and troubleshooting > 8) SFN agrees to provide configuration access and snmp access to the > MICE technical committee to ease troubleshooting and to provide > publicly available graphing. > > Thanks! > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io <mailto:jayhanke@southfront.io> > Phone 612-204-0000 -- Richard

3 3

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