January 2024 - mice-discuss - lists.micemn.net

Please welcome T-Mobile USA, Inc to MICE!
by Jeremy Lumby Aug. 8, 2025

Aug. 8, 2025

Name: T-Mobile USA, Inc Switch: MICE Main Port: Ethernet 6/15/1 ASN: 21928 IPv4: This is a port addition to an existing LAG, all IP info remains the same. The new connection will be 3x100G IPv6: Peering Contact: peering(a)t-mobile.com Route Servers: Yes BFD: No Welcome Aboard Again! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

2 7

Please welcome Qwilt Inc. to MICE!
by Jeremy Lumby May 15, 2025

May 15, 2025

Name: Qwilt Inc. Switch: MICE Main Ports: 6/29/1 ASN: 20253 IPv4: 206.108.255.202/24 IPv6: 2001:504:27:0:0:4F1D::1/64 Peering Contact: peering(a)qwilt.com Route Servers: YES BFD: NO Welcome Aboard! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

4 50

Please welcome Hiawatha Broadband Communications to MICE!
by Jeremy Lumby May 9, 2025

May 9, 2025

Name: Hiawatha Broadband Communications Switch: MICE Core Port: E5/41 ASN: 14828 IPv4: IPs remain the same. This is a port addition bringing capacity to 40G on portchannel 32 IPv6: Peering Contact: noc(a)hbci.com Route Servers: YES BFD: YES Welcome Aboard Again! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 Fax: 952-873-7425 jlumby(a)mnvoip.com

3 21

Please welcome Express Data Solutions LLC to MICE!
by Jeremy Lumby Dec. 13, 2024

Dec. 13, 2024

Name: Express Data Solutions LLC Switch: MICE MAIN Port: Ethernet4/2 ASN: 31834 IPv4: 206.108.255.183/24 IPv6: 2001:504:27:0:0:7C5A::1/64 Peering Contact: peering(a)express-ds.com Route Servers- Yes BFD: Yes Welcome Aboard! Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 M: 612-355-7740 D: 612-392-6814 F: 952-873-7425 jlumby(a)mnvoip.com

3 10

IRR Mandatory at MICE / New Route Servers
by Richard Laager Feb. 27, 2024

Feb. 27, 2024

[I plan to send this to MICE-ANNOUNCE too, but I want to see if anyone has corrections.] MICE will soon be deploying new route servers which will require IRR (Internet Routing Registry) records, as is a best practice at IXPs. *What* * You MUST have an as-set object listing your AS and your downstream ASes (if any). o You MUST either list that as-set in PeeringDB or email the name of your as-set to me (off-list to rlaager(a)wiktel.com please). * A route/route6 object MUST exist for each prefix you announce to the route servers (whether originated by you or transited through you) and it must list an Origin AS that is in your as-set. *When* * *If you are a transit AS (i.e. have ASes behind you) and don't have an /as-set/ object, fix this **/now/**.* Without an as-set object, your downstream ASes announcements will be blocked (filtered) immediately when the /first/ new route server is cut in. (Granted, they will still work through the second route server until it is upgraded.) Figure you have 1-2 weeks at most. * Enforcement of the route/route6 objects (for both transit and non-transit ASes) will come later, but not a lot later. So please, start on this now. ** *Where* If you are not sure /where/ to create IRR records, use ARIN (assuming you are in the ARIN region). *How (with ARIN)* 1. Login to ARIN Online. (Go to arin.net and click Login in the top right.) 2. On the left side, expand "Routing Security" and click "IRR". 3. Click "as-set" at the top. 4. Click "Create an Object". 5. Fill in the fields: The "AS Set Name" is what you will list in PeeringDB (or email to me). "Description" is unparsed, but they suggest the location and have a button to "Copy the Address from My Org ID". "Members" is where you list your ASN and downstream ASes (if any). 6. Click "Review". Once ready, click "Submit". 7. Click "route/route6" at the top. 8. Click "Create an Object". 9. Fill in the fields: "Prefix" is the prefix, e.g. 192.0.2.0/24. "Origin" is your ASN. 10. Click "Review". Once ready, click "Submit". 11. Repeat to create additional route objects until all of your announcements are covered. Don't forget IPv6! *Examples* Here is my as-set: https://www.radb.net/query?keywords=AS-WIKTEL Here is one example route: https://www.radb.net/query?keywords=69.89.192.0%2F20 (I created the AS33362 one. The AS19905 one is because another AS can originate this route for DDoS scrubbing reasons.) -- Richard

10 34

MICE Core Switch EOS Upgrade
by Richard Laager Feb. 7, 2024

Feb. 7, 2024

Date & Time Wednesday, January 31 at 06:00 US/Central Description Jeremy will upgrade software on the Arista core switch at 511. This is necessary to be able to install the (newer) 100G card into the switch. Rollback Plan The previous software image will be available to revert. -- Richard

3 5

Addresses on the list...
by Mike Horwath Jan. 31, 2024

Jan. 31, 2024

Calling out: From: Tritan Internet LLC (AS393577) <noc(a)as393577.net> Subject: TD#937 - Acknowledgement from Tritan Internet NOC Please subscribe either a user to the list or update things so that autoresponses do not occur. LISTSERV picked it up and did the right thing, thankfully. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

1 0

BGP ADD-PATH capability
by Richard Laager Jan. 24, 2024

Jan. 24, 2024

I propose that MICE enable BGP ADD-PATH capability (RFC 7911) on the route servers (in TX mode only). This is negotiated BGP capability, so we do not need any per-participant setting for it. ADD-PATH is useful if the best path route is being filtered but another route would not be. We discussed adding this at a UG meeting years ago. There are other IXPs that have this enabled. For example, this one: https://www.bcix.de/ixp/content/0/route-servers In terms of timeline, I propose something like this: * January 9: Enable it on Route Server 1. * January 16: Enable it on Route Server 2. The actual change looks like this for the RS1-only piece, and then the conditional would be removed when we want to deploy to RS2: --- a/roles/ixpmanager/files/mice/api/v4/router/server/bird2/neighbors.foil.php +++ b/roles/ixpmanager/files/mice/api/v4/router/server/bird2/neighbors.foil.php @@ -315,6 +315,9 @@ protocol bgp pb_<?= $int['fvliid'] ?>_as<?= $int['autsys'] ?> from tb_rsclient { import filter f_import_as<?= $int['autsys'] ?>; table t_<?= $int['fvliid'] ?>_as<?= $int['autsys'] ?>; export filter f_export_as<?= $int['autsys'] ?>; +<?php if( $t->router->router_id == "206.108.255.1" ): ?> + add paths tx; +<?php endif; ?> }; <?php if( $int['bgpmd5secret'] && !$t->router->skip_md5 ): ?> password "<?= $int['bgpmd5secret'] ?>"; -- Richard

6 11

MICE Maintenance 2024-01-18 & 2024-01-19
by Richard Laager Jan. 9, 2024

Jan. 9, 2024

Date & Time January 18, 00:00 - 05:00 US/Central January 19, 00:00 - 05:00 US/Central Description Our underlying fiber provider will be doing maintenance on the connection from 511 to Ridgeview. They are attempting to repair some other fiber issues. We may or may not go down. If we did go down, participants on the 511 side would see a loss of BGP to Route Server 2. -- Richard

1 0

Route servers?
by Miles McCredie Jan. 3, 2024

Jan. 3, 2024

FWIW, the AS11232 sessions to route server 2 have been active for about 25 minutes. https://ixpmgr.micemn.net/lg/rs2-ipv4 and https://ixpmgr.micemn.net/lg/rs2-ipv6 <https://ixpmgr.micemn.net/lg/rs2-ipv6%20show%20that%20AS11232> show quite a few other ASNs that are not established. https://ixpmgr.micemn.net/lg/rs1-ipv4 and https://ixpmgr.micemn.net/lg/rs1-ipv6 show more not-established sessions than I would expect but fewer than rs2. I haven't looked more closely at the impact to routing yet. Any details about the work in progress? Thanks [http://images.midcocomm.com/ES_MidcoLogo.png] Miles McCredie Principal Network Engineer II-Core IP Office: 6052755192 Miles.McCredie(a)midco.com Midco.com

4 6