- mice-discuss - lists.micemn.net

Re: Route Server Session Cleanup

by Jay Hanke

We've had several members request adding sessions after the initial paperwork and the website doesn't always get updated to reflect the new status. The website members list will soon be generated from the ixp manager database rather than being manually updated. We are reaching out to networks with mismatches. On Sun, May 28, 2023, 11:35 AM David Farmer <farmer(a)umn.edu> wrote: > I’d note that GigaMonster is listed as not being a route server > participant on the MICE participant page. > > So, I think that is intentional on there part. > > Thanks > > On Sun, May 28, 2023 at 11:15 Jay Hanke <jayhanke(a)southfront.io> wrote: > >> Following the migration to the route server last week we have a number >> of members with down or misconfigured BGP sessions. We have reached >> out to each member via email and will be disabling the route server >> sessions to RS1 of the following members on Thursday June 1st, 2023 if >> we do not get a response or resolution. >> >> >> AS13737 - INCX Global, LLC >> AS29762 - Emergent Networks >> AS30110 - Advanced Communications Technology >> AS31939 - GigaMonster >> AS32029 - Lakana, a division of Nexstar Broadcasting >> >> >> -- >> Jay Hanke, President >> South Front Networks >> jayhanke(a)southfront.io >> Phone 612-204-0000 >> https://southfront.io/path.html >> http://peeringsummit.com <--- Des Moines July 17-18, 2023 >> > -- > =============================================== > David Farmer Email:farmer@umn.edu > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== >

May 28, 2023

Re: Route Server Session Cleanup

by David Farmer

I’d note that GigaMonster is listed as not being a route server participant on the MICE participant page. So, I think that is intentional on there part. Thanks On Sun, May 28, 2023 at 11:15 Jay Hanke <jayhanke(a)southfront.io> wrote: > Following the migration to the route server last week we have a number > of members with down or misconfigured BGP sessions. We have reached > out to each member via email and will be disabling the route server > sessions to RS1 of the following members on Thursday June 1st, 2023 if > we do not get a response or resolution. > > > AS13737 - INCX Global, LLC > AS29762 - Emergent Networks > AS30110 - Advanced Communications Technology > AS31939 - GigaMonster > AS32029 - Lakana, a division of Nexstar Broadcasting > > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 > https://southfront.io/path.html > http://peeringsummit.com <--- Des Moines July 17-18, 2023 > -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

May 28, 2023

Route Server Session Cleanup

by Jay Hanke

Following the migration to the route server last week we have a number of members with down or misconfigured BGP sessions. We have reached out to each member via email and will be disabling the route server sessions to RS1 of the following members on Thursday June 1st, 2023 if we do not get a response or resolution. AS13737 - INCX Global, LLC AS29762 - Emergent Networks AS30110 - Advanced Communications Technology AS31939 - GigaMonster AS32029 - Lakana, a division of Nexstar Broadcasting -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 https://southfront.io/path.html http://peeringsummit.com <--- Des Moines July 17-18, 2023

May 28, 2023

Limelight Networks Removed from MICE Route Server Config

by Jay Hanke

Limelight Networks is no longer utilizing the MICE route servers. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 https://southfront.io/path.html http://peeringsummit.com <--- Des Moines July 17-18, 2023

May 25, 2023

MICE RS1 Route Server Cleanup

by Jay Hanke

We are going through a process to clean up the configurations on the new RS1 server located in 511. The config is now automated and IRR/RPKI filtering is in place. We're currently working on the IPv4 sessions. There are several networks that have Route Server sessions that are currently not up. AS13737 - INCX Global, LLC AS22768 - Synergy Fiber AS22822 - Limelight Networks Global AS26794 - Dakota Carrier Network (206.108.255.60 Route Limit Exceeded) AS29762 - Emergent Networks AS30110 - Advanced Communications Technology (Route Limit Exceeded) AS31939 - GigaMonster AS32029 - Lakana AS32097 - Wholesale Internet, Inc. AS32867 - Long Lines Communications AS397324 - Celerity Networks Max Prefixes (used for Route Limit) are pulled from Peeringdb.com. Networks can check their status on the new looking glass (Thanks Richard!): https://ixpmgr.micemn.net/lg/rs1-ipv4 If your network is no longer utilizing the route servers please email peering(a)micemn.net so we can update your configuration. Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 https://southfront.io/path.html http://peeringsummit.com <--- Des Moines July 17-18, 2023

May 24, 2023

Land O Lakes left MICE

by Jay Hanke

Land O Lakes has disconnected from MICE. IXP Manager has been updated. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 https://southfront.io/path.html http://peeringsummit.com <--- Des Moines July 17-18, 2023

May 24, 2023

Re: IRR Mandatory at MICE / New Route Servers

by Richard Laager

On 2023-05-13 01:30, Richard Laager wrote: > I am currently allowing the following sources across the board: > ARIN,RIPE,LACNIC,APNIC,AFRINIC,RADB,NTTCOM,LEVEL3 Change as of today: ARIN,RIPE,LACNIC,APNIC,AFRINIC,RADB,*ALTDB,*NTTCOM,LEVEL3 -- Richard

May 23, 2023

Re: IRR Mandatory at MICE / New Route Servers

by Richard Laager

I added some bits about IXP Manager and IRR to the website: https://micemn.net/technical.html I also updated the communities bit to reflect what the new route servers will support. Suggestions welcome. -- Richard

May 23, 2023

Re: IRR Mandatory at MICE / New Route Servers

by Richard Laager

This is the current cutover plan: Phase 1: On Tuesday, May 23, starting around 10:00 AM US/Central, we will upgrade route server 1. It will enforce the IRR as-set requirement for transit ASes, but will NOT enforce the IRR prefix requirement. Since route server 2 will still exist, even the as-set requirement is only a soft requirement. Phase 2: On Wednesday, May 31, starting around 10:00 AM US/Central, we will upgrade route server 2. It will be fully enforcing. At that point, the as-set requirement will be a hard requirement. The prefix IRR requirement will still be a soft requirement, as route server 1 will still not be enforcing. Phase 3: Tentatively, on Wednesday, June 7, starting around 10:00 AM US/Central, we will configure route server 1 to be fully enforcing. At that point, all IRR requirements will hard requirements. This date is subject to change based on what we see filtered. *We ask that you do /not/ take down your route server BGP sessions for these changes, as that will make it harder for us to know if things are working. If you are going to do so (e.g. because your organization's policies require it), then please let me know so I can expect your session to be down.* -- Richard

May 13, 2023

Re: IRR Mandatory at MICE / New Route Servers

by Richard Laager

I am currently allowing the following sources across the board: ARIN,RIPE,LACNIC,APNIC,AFRINIC,RADB,NTTCOM,LEVEL3 On 2023-05-12 11:14, Michael Hare wrote: > It also handles the $REGISTRY::$THING model. Thanks for the tip! I switched from bgpq3 to bgpq4. IXP Manager doesn't support bgpq4, but the only difference was one flag. I used a wrapper script for now, and filed a feature request with IXP Manager: https://github.com/inex/IXP-Manager/issues/844 Arnold Nipper, via the IXP Manager mailing list, gave me an example of how to get this information out of PeeringDB. With that, I was able to write a script to interact with the IXP Manager database. It pulls the current settings from IXP Manager, pulls from PeeringDB, reports any changes, updates IXP Manager, and triggers the ASN & prefix updates in IXP Manager. I have that set to run hourly. The route servers will update their configuration hourly, offset by 30 minutes. That is, route server 1 will update at xx:08 and route server 2 will update at xx:38. -- Richard

May 13, 2023