- mice-announce - lists.micemn.net

MICE Core Switch Card Upgrade
by Richard Laager Feb. 8, 2024

Feb. 8, 2024

Date & Time Wednesday, February 14 at 15:00 US/Central Description Jeremy will swap a (now unused) 10G line card for a 100G line card in the Arista core switch at 511. There is no expected impact for most participants. In the (relatively unlikely) event that a fiber cable is physically in the way and he has to unplug it to remove/install the card, he will disable BGP for that participant first and wait (unless the port is part of a LAG with sufficient excess capacity at that time of day). The Fiber Minnesota and Minnesota VoIP remote switches are connected by 3x100G LAG. Jeremy will move one port from each LAG from card 6 to the new card. Rollback Plan If there is some problem, the new 100G card can be removed. The ports in the Fiber Minnesota and Minnesota VoIP remote switches can be moved back to card 6. -- Richard ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 0

MICE Core Switch EOS Upgrade
by Richard Laager Jan. 30, 2024

Jan. 30, 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 ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 1

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 ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 0

UG 44 Meeting & Election
by Richard Laager Oct. 25, 2023

Oct. 25, 2023

The MICE UG 44 meeting will be held Wednesday, October 25, 3:00 pm at UMN. Here are the details (parking, etc.) from last time: https://lists.iphouse.net/cgi-bin/wa?A2=MICE-DISCUSS;2c503e19.2209 An updated Zoom link will be coming. *Nominations* 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, Anthony's seat is up for election. As in the past, we will close nominations in advance of the meeting so people have a chance to instruct a proxy appropriately. *Nominations will be open for two weeks (so until the end of October 7).* * * *Proxies * The bylaws state that you send proxies to the Chief Manager (me, Richard Laager), and electronic means are acceptable. So a simple email is sufficient: rlaager(a)wiktel.com or chiefmanager(a)micemn.net. If you send me a /vote/ by email (e.g. "We vote for <X>."), I will treat it as an a proxy appointment, appointing me to vote on your behalf, but restricted to /only/ the election item and to /only/ vote for the candidate you expressed. If you send me a proxy with different instructions (e.g. "We appoint <Y> to vote for us."), obviously that will be honored as written. -- Richard ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 2

Re: RPKI ROAs
by Richard Laager June 21, 2023

June 21, 2023

I intend to publish the following ROAs on MICE's behalf to indicate that the peering LAN is not to appear in the Internet routing table: On Monday (June 19) around 10:00 AM: 2001:504:27::/48 AS0 maxLength 128 On Wednesday (June 21) around 10:00 AM: 206.108.255.0/24 AS0 maxLength 32 The reason for the maxLength is: "By convention, an AS 0 ROA should have a maxLength value of 32 for IPv4 addresses and a maxlength value of 128 for IPv6 addresses" -- RFC 6483, section 4. This should only be an issue for someone if they are advertising the MICE peering subnet in their iBGP (which we discourage) and are doing RPKI validation of that iBGP (which seems unlikely). If you think this will be a problem for you, let me know. -- Richard ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 2

Re: IRR Mandatory at MICE / New Route Servers
by Richard Laager June 14, 2023

June 14, 2023

After finishing up with the last minute inquiries, I deployed these changes. As far as I am aware, for everyone that has been in contact with me, things are either: A) resolved, B) been given an exception, or C) are irrelevant (see the "don't count") at the end of this email. The things that are filtered should only be people who never responded. The following routes are being filtered on rs1 (and rs2). That is, this is what is effectively "blocked" (for lack of route/route6 objects, ignoring rejections for other causes) /excluding/ the 4 exceptions: AS5056: https://ixpmgr.micemn.net/lg/rs1-ipv4/routes/protocol/pb_0047_as5056 206.83.43.0/24 AS5056 AS6939: Too many routes to list. They have looser IRR policies <https://routing.he.net/algorithm.html> (specifically, I think the RIR handle matches allow a lot that traditional IRR filtering does not). Bilateral with them if you want those. AS10242: https://ixpmgr.micemn.net/lg/rs1-ipv4/routes/protocol/pb_0028_as10242 23.130.82.0/24 AS398200 AS11796: https://ixpmgr.micemn.net/lg/rs1-ipv4/routes/protocol/pb_0051_as11796 192.236.20.0/24 AS25958 192.236.21.0/24 AS25958 https://ixpmgr.micemn.net/lg/rs1-ipv6/routes/protocol/pb_0051_as11796 2604:f9c0::/32 AS397064 AS16851: https://ixpmgr.micemn.net/lg/rs1-ipv4/routes/protocol/pb_0060_as16851 170.31.248.0/21 AS27534 170.31.160.0/23 AS27534 AS22402: https://ixpmgr.micemn.net/lg/rs1-ipv4/routes/protocol/pb_0088_as22402 206.11.94.0/24 AS22402 AS27204: https://ixpmgr.micemn.net/lg/rs1-ipv4/routes/protocol/pb_0095_as27204 198.98.192.0/21 AS396853 AS40413: https://ixpmgr.micemn.net/lg/rs1-ipv4/routes/protocol/pb_0076_as40413 207.250.207.0/24 AS40413 198.204.66.0/24 AS40413 AS393639: https://ixpmgr.micemn.net/lg/rs1-ipv4/routes/protocol/pb_0112_as393639 192.55.242.0/23 AS393639 These don't really count: AS26794: https://ixpmgr.micemn.net/lg/rs1-ipv4/routes/protocol/pb_0048_as26794 208.85.166.0/24 AS40569 -- IP space and AS recently removed from WHOIS. 208.85.167.0/24 AS40569 -- IP space and AS recently removed from WHOIS. AS55009: https://ixpmgr.micemn.net/lg/rs1-ipv4/routes/protocol/pb_0002_as55009 69.57.200.0/24 AS400080 -- This is going away and they will pull the announcement tomorrow. -- Richard ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 0

Re: IRR Mandatory at MICE / New Route Servers
by Richard Laager June 7, 2023

June 7, 2023

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 ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 6

Re: IRR Mandatory at MICE / New Route Servers
by Richard Laager May 11, 2023

May 11, 2023

On 2023-05-09 05:19, Richard Laager wrote: > > 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.) > For more discussion, see the thread on MICE-DISCUSS: https://lists.iphouse.net/cgi-bin/wa?A2=ind2305&L=MICE-DISCUSS&T=0&F=&S=&P=… <https://lists.iphouse.net/cgi-bin/wa?A2=ind2305&L=MICE-DISCUSS&T=0&F=&S=&P=…> -- Richard ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 0

MICE User Group 43 - Meeting Reminder
by Richard Laager April 15, 2023

April 15, 2023

> From: AnthonyAnderberg(a)nuvera.net > > As a reminder: MICE’s user group meeting #43 will be next Wednesday April 19 at 3:00pm CDT. > > The meeting is being hosted by USI at their Ridgeview data center: 12450 Wayzata Blvd, Minnetonka MN > For those dialing in remotely the bridge will be: 1-952-562-5400 - passcode 6423 (mice) > > USI offices are on the third floor in suite #315, their conference room is #301 next to the south stairwell. > There is free public parking all around the building, with free overflow parking across the street to the north of the building. > You can get up to the third floor from either the south or north entrances, the elevator is on the north side of the building. > Public restrooms are on the second and third floors in the main hallways. > > If anyone wants a tour of the data center USI will be giving tours on demand starting at 2pm starting in the conference room, and they will likely be able to fit in a tour after our meeting too while everyone is debating supper plans. > > We’ve made progress on a number of items talked about last meeting but don’t have any new agenda items at this time. > > Thanks everyone, > Anthony ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 0

MICE UG 40
by Richard Laager Sept. 20, 2022

Sept. 20, 2022

Note: Change of date and moving to online. MICE UG 40 will be March 11 at 3:00 PM, held online. This will be the usual business meeting plus voting on bylaws changes. On March 16, the previously scheduled date, those of us at MTA (and anyone else interested, of course) will get together for a MICE social. Details TBD. -- Richard ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

1 2