- mice-discuss - lists.micemn.net

Re: Maintenance: ZAYO TTN-0005095553 Planned

by Jesse Reed

Our (AcenTek’s) traffic completely stopped between 00:00 – 02:30 CST this morning to both of our HE.net peerings (at Rochester). We did not lose our BGP session(s) however. Anybody else see similar behavior or get a RFO back yet? Thanks, Jesse From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of AnthonyAnderberg(a)nuvera.net Sent: Friday, July 9, 2021 1:29 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] FW: Maintenance: ZAYO TTN-0005095553 Planned EXTERNAL: This email originated from a sender outside AcenTek. Do not click links or open attachments unless you recognize the sender and know the content is safe. Looks like the Zayo maintenance below is affecting a number of MICE members, no updated ETR from them at the moment. Additionally, another maintenance event seems to be affecting HE’s Rochester location starting at midnight - hope everyone is doing OK. Cheers, anthony [signature_2077243253] From: MR Zayo <mr(a)zayo.com> Date: Thursday, July 8, 2021 at 10:01 PM Subject: START MAINTENANCE NOTIFICATION***Nuvera Communications***ZAYO TTN-0005095553 Planned*** Dear Zayo Customer, Please be advised that the below scheduled maintenance activity will be commencing momentarily. Maintenance Ticket #: TTN-0005095553 Maintenance Window 1st Activity Date 08-Jul-2021 22:00 to 09-Jul-2021 06:00 ( Central ) 09-Jul-2021 03:00 to 09-Jul-2021 11:00 ( GMT ) Location of Maintenance: 5200' east of Kelly Ave on County Rd 140 in Cologne, MN Reason for Maintenance: Zayo will perform maintenance to replace a box culvert on County Rd 140 in Cologne, MN. Circuit(s) Affected: Circuit Id Expected Impact A Location Address Z Location Address Legacy Circuit Id FBDK/1363902//ZFS Hard Down - Duration of maintenance window If you have any questions or need any additional information, please contact the MR group at mr(a)zayo.com or call 866-236-2824. Regards, Zayo Global Change Management Team/Équipe de Gestion du Changement Global Zayo Zayo | Our Fiber Fuels Global Innovation Toll free/No sans frais: 1.866.236.2824 United Kingdom Toll Free/No sans frais Royaume-Uni: 0800.169.1646 Email/Courriel: mr(a)zayo.com<mailto:releases@zayo.com> Website/Site Web: https://www.zayo.com<http://www.zayo.com/> Purpose<http://www.zayo.com/company/about-zayo/> | Network Map<http://www.zayo.com/solutions/global-network/> | Escalation List<https://tranzact.zayo.com/#!/escalation-lists> | LinkedIn<https://www.linkedin.com/company/530962/> | Twitter<https://twitter.com/zayogroup> | Tranzact <https://tranzact.zayo.com/#!/login> This communication is the property of Zayo and may contain confidential or privileged information. If you have received this communication in error, please promptly notify the sender by reply e-mail and destroy all copies of the communication and any attachments. ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

July 9, 2021

FW: Maintenance: ZAYO TTN-0005095553 Planned

by AnthonyAnderberg＠nuvera.net

Looks like the Zayo maintenance below is affecting a number of MICE members, no updated ETR from them at the moment. Additionally, another maintenance event seems to be affecting HE’s Rochester location starting at midnight - hope everyone is doing OK. Cheers, anthony [signature_2077243253] From: MR Zayo <mr(a)zayo.com> Date: Thursday, July 8, 2021 at 10:01 PM Subject: START MAINTENANCE NOTIFICATION***Nuvera Communications***ZAYO TTN-0005095553 Planned*** Dear Zayo Customer, Please be advised that the below scheduled maintenance activity will be commencing momentarily. Maintenance Ticket #: TTN-0005095553 Maintenance Window 1st Activity Date 08-Jul-2021 22:00 to 09-Jul-2021 06:00 ( Central ) 09-Jul-2021 03:00 to 09-Jul-2021 11:00 ( GMT ) Location of Maintenance: 5200' east of Kelly Ave on County Rd 140 in Cologne, MN Reason for Maintenance: Zayo will perform maintenance to replace a box culvert on County Rd 140 in Cologne, MN. Circuit(s) Affected: Circuit Id Expected Impact A Location Address Z Location Address Legacy Circuit Id FBDK/1363902//ZFS Hard Down - Duration of maintenance window If you have any questions or need any additional information, please contact the MR group at mr(a)zayo.com or call 866-236-2824. Regards, Zayo Global Change Management Team/Équipe de Gestion du Changement Global Zayo Zayo | Our Fiber Fuels Global Innovation Toll free/No sans frais: 1.866.236.2824 United Kingdom Toll Free/No sans frais Royaume-Uni: 0800.169.1646 Email/Courriel: mr(a)zayo.com<mailto:releases@zayo.com> Website/Site Web: https://www.zayo.com<http://www.zayo.com/> Purpose<http://www.zayo.com/company/about-zayo/> | Network Map<http://www.zayo.com/solutions/global-network/> | Escalation List<https://tranzact.zayo.com/#!/escalation-lists> | LinkedIn<https://www.linkedin.com/company/530962/> | Twitter<https://twitter.com/zayogroup> | Tranzact <https://tranzact.zayo.com/#!/login> This communication is the property of Zayo and may contain confidential or privileged information. If you have received this communication in error, please promptly notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

July 9, 2021

Versus Port 10G Upgrade

by Jay Hanke

Versus is upgrading to 10G New Port: MN VoIP 10g :: Ethernet21 Old Port: MICE Main 1G :: ge-0/0/18 All IP information will remain the same. The old port can be decommissioned at migration. Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

July 7, 2021

Zayo Belle Plaine

by Jeremy Lumby

Just an FYI Zayo is having cooling issues in Belle Plaine again. In the past this has caused the MICE extension switch to power itself off as a result of over temperature protection. I have opened a ticket with Zayo. The temperature has increased 20F in the last 45 minutes. 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

July 5, 2021

Re: Please Welcome Involta to MICE!

by Doug McIntyre

On Thu, Jun 24, 2021 at 11:58:04AM -0500, Jay Hanke wrote: >Name: Involta >Switch: Compudyne Duluth Remote >Port: xe-0/0/3 >ASN: 14230 >IPv4: 206.108.255.180/24 >IPv6: 2001:504:27::3796:0:1/64 >Peering Contact: peering(a)involta.com >Route Servers- Yes >BFD: NO I've got them added into the RR's. Welcome!

June 24, 2021

Please Welcome Involta to MICE!

by Jay Hanke

Name: Involta Switch: Compudyne Duluth Remote Port: xe-0/0/3 ASN: 14230 IPv4: 206.108.255.180/24 IPv6: 2001:504:27::3796:0:1/64 Peering Contact: peering(a)involta.com Route Servers- Yes BFD: NO Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

June 24, 2021

Re: EIDG

by AnthonyAnderberg＠nuvera.net

Done, and I copied the original single-port data over the top of the po4 interface data to preserve a sense of history. Cheers, anthony On 6/22/21, 7:21 AM, "MICE Discuss on behalf of Jay Hanke" <MICE-DISCUSS(a)LISTS.IPHOUSE.NET on behalf of jayhanke(a)SOUTHFRONT.IO> wrote: EIDG has completed the upgrade to 1x2x10G SFN Remote Switch Eth9 Eth15 Port Channel 4 Anthony, could you update graphing? -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

June 22, 2021

EIDG

by Jay Hanke

EIDG has completed the upgrade to 1x2x10G SFN Remote Switch Eth9 Eth15 Port Channel 4 Anthony, could you update graphing? -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

June 22, 2021

Re: Twins Game After MICE Meeting?

by AnthonyAnderberg＠nuvera.net

I just purchased Section 4 Row 9 Seats 9-11 for my wife and I plus one for whoever else might want. Looks like there are two seats left on that side in Row 10, and 4 in row 12. On 6/19/21, 8:40 AM, "MICE Discuss on behalf of Mike Johnston" <MICE-DISCUSS(a)LISTS.IPHOUSE.NET on behalf of mjohnston(a)WIKTEL.COM> wrote: My wife has acquired tickets for her, me, and my younger daughter. Section 4, Row 9, Seats 12,13,14. Mike Johnston Wiktel

June 22, 2021

Re: Jumbo Frames

by Jamison Masters

Thanks everyone. Safe word: “1500 bytes.“ Gratefully, Jamison From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Ben Wiechman Sent: Friday, June 18, 2021 2:57 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Jumbo Frames I use MTU 9000* on all my router-to-router links because I need to be able to carry larger-than-1500-byte circuit traffic. If nothing else, circuit VLANs all need to be a bit over 1500 bytes on the outside (i.e. with my tags and possibly tags of other carriers involved) so that they are 1500 bytes on the inside. * Maybe I should/will-need-to change this to 9000 + a bit to allow for 9000 inside. We don't typically see carriers looking for anything greater than about 2000 bytes in practice, though we also follow a similar 9000 byte configuration on our internal transport links. 1500 to the internet edge. You could fiddle with the MTU to eek out a few extra bytes for circuits, but what you're doing today already ~4x the real world use cases that we've seen. Maybe experiences differ for providers that carry a lot of traffic between data centers. Ben Wiechman Director of IP Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com<mailto:ben.wiechman@arvig.com> Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com<http://arvig.com> On Fri, Jun 18, 2021 at 2:53 PM Richard Laager <rlaager(a)wiktel.com<mailto:rlaager@wiktel.com>> wrote: On 6/18/21 2:16 PM, Jonathan Stewart wrote: Finally, views do differ, i'm sure others have opinions that do not match mine. I don't see anything wrong in what you said. I'll add some detail on what we're doing in case it's helpful (or if someone can educate me if I'm doing something bad): I use MTU 9000 on my transit connections, coordinated with the transit provider, because there seems to be no harm in doing that. I use MTU 9000* on all my router-to-router links because I need to be able to carry larger-than-1500-byte circuit traffic. If nothing else, circuit VLANs all need to be a bit over 1500 bytes on the outside (i.e. with my tags and possibly tags of other carriers involved) so that they are 1500 bytes on the inside. * Maybe I should/will-need-to change this to 9000 + a bit to allow for 9000 inside. I'm 1500 bytes at the customer edge for Internet. I'm also 1500 bytes at IXes. -- Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 19, 2021

Re: Twins Game After MICE Meeting?

by Travis Fincham

We have 4 that would be coming Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Mike Johnston <mjohnston(a)WIKTEL.COM> Sent: Saturday, June 19, 2021 8:40:23 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: [EXTERNAL]Re: [MICE-DISCUSS] Twins Game After MICE Meeting? Warning: This email originated from outside of Key Cooperative. DO NOT click on links or open attachments unless you recognize the sender and know the content is safe. My wife has acquired tickets for her, me, and my younger daughter. Section 4, Row 9, Seats 12,13,14. Mike Johnston Wiktel ________________________________ NOTICE: This message (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. § 2510-2521, is CONFIDENTIAL, and is intended only for the individual to whom it is addressed. If you are not the named addressee or an employee or agent responsible for delivering this message to the named addressee, you are hereby notified that you have received this message in error and that any review, retention, dissemination, distribution, copying or use of this communication is strictly prohibited. Please reply to the sender that you received this message in error and then delete it.

June 19, 2021

Re: Twins Game After MICE Meeting?

by Mike Johnston

My wife has acquired tickets for her, me, and my younger daughter. Section 4, Row 9, Seats 12,13,14. Mike Johnston Wiktel

June 19, 2021

Re: Twins Game After MICE Meeting?

by Mike Johnston

Has anybody else shown interest? Travis Fincham?

June 19, 2021

Re: Twins Game After MICE Meeting?

by Reid Fishler

No, I was waiting to see who wanted to come... Reid On Fri, Jun 18, 2021, 11:28 PM Mike Johnston <mjohnston(a)wiktel.com> wrote: > Have you already purchased some tickets? If so, where are your seats? > > mjohnston(a)wiktel.com if you want to go off-list. > > > On 2021-06-18 22:18, Reid Fishler wrote: > > There are seats RIGHT behind the twins dugout. On the twins site. > > Reid > > On Fri, Jun 18, 2021, 11:15 PM Mike Johnston <mjohnston(a)wiktel.com> wrote: > >> Good idea! Me, my wife, and one of my daughters are interested in >> going. I suppose it would be best if all interested MICEonians have >> adjacent seats. My wife is fussy...she wants good seats. >> >> > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

June 19, 2021

Re: Twins Game After MICE Meeting?

by Mike Johnston

Have you already purchased some tickets? If so, where are your seats? mjohnston(a)wiktel.com if you want to go off-list. On 2021-06-18 22:18, Reid Fishler wrote: > There are seats RIGHT behind the twins dugout. On the twins site. > > Reid > > On Fri, Jun 18, 2021, 11:15 PM Mike Johnston <mjohnston(a)wiktel.com > <mailto:mjohnston@wiktel.com>> wrote: > > Good idea! Me, my wife, and one of my daughters are interested in > going. I suppose it would be best if all interested MICEonians have > adjacent seats. My wife is fussy...she wants good seats. > > > ------------------------------------------------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> >

June 19, 2021

Re: Twins Game After MICE Meeting?

by Reid Fishler

There are seats RIGHT behind the twins dugout. On the twins site. Reid On Fri, Jun 18, 2021, 11:15 PM Mike Johnston <mjohnston(a)wiktel.com> wrote: > Good idea! Me, my wife, and one of my daughters are interested in > going. I suppose it would be best if all interested MICEonians have > adjacent seats. My wife is fussy...she wants good seats. > >

June 19, 2021

Re: Twins Game After MICE Meeting?

by Mike Johnston

Good idea! Me, my wife, and one of my daughters are interested in going. I suppose it would be best if all interested MICEonians have adjacent seats. My wife is fussy...she wants good seats.

June 19, 2021

Re: Jumbo Frames

by Ben Wiechman

> > I use MTU 9000* on all my router-to-router links because I need to be able > to carry larger-than-1500-byte circuit traffic. If nothing else, circuit > VLANs all need to be a bit over 1500 bytes on the outside (i.e. with my > tags and possibly tags of other carriers involved) so that they are 1500 > bytes on the inside. * Maybe I should/will-need-to change this to 9000 + a > bit to allow for 9000 inside. We don't typically see carriers looking for anything greater than about 2000 bytes in practice, though we also follow a similar 9000 byte configuration on our internal transport links. 1500 to the internet edge. You could fiddle with the MTU to eek out a few extra bytes for circuits, but what you're doing today already ~4x the real world use cases that we've seen. Maybe experiences differ for providers that carry a lot of traffic between data centers. Ben Wiechman Director of IP Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com On Fri, Jun 18, 2021 at 2:53 PM Richard Laager <rlaager(a)wiktel.com> wrote: > On 6/18/21 2:16 PM, Jonathan Stewart wrote: > > Finally, views do differ, i'm sure others have opinions that do not match > mine. > > I don't see anything wrong in what you said. I'll add some detail on what > we're doing in case it's helpful (or if someone can educate me if I'm doing > something bad): > > I use MTU 9000 on my transit connections, *coordinated with the transit > provider*, because there seems to be no harm in doing that. > > I use MTU 9000* on all my router-to-router links because I need to be able > to carry larger-than-1500-byte circuit traffic. If nothing else, circuit > VLANs all need to be a bit over 1500 bytes on the outside (i.e. with my > tags and possibly tags of other carriers involved) so that they are 1500 > bytes on the inside. * Maybe I should/will-need-to change this to 9000 + a > bit to allow for 9000 inside. > > I'm 1500 bytes at the customer edge for Internet. I'm also 1500 bytes at > IXes. > > -- > Richard > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

June 18, 2021

Re: Jumbo Frames

by Richard Laager

On 6/18/21 2:16 PM, Jonathan Stewart wrote: > > Finally, views do differ, i'm sure others have opinions that do not > match mine. > I don't see anything wrong in what you said. I'll add some detail on what we're doing in case it's helpful (or if someone can educate me if I'm doing something bad): I use MTU 9000 on my transit connections, /coordinated with the transit provider/, because there seems to be no harm in doing that. I use MTU 9000* on all my router-to-router links because I need to be able to carry larger-than-1500-byte circuit traffic. If nothing else, circuit VLANs all need to be a bit over 1500 bytes on the outside (i.e. with my tags and possibly tags of other carriers involved) so that they are 1500 bytes on the inside. * Maybe I should/will-need-to change this to 9000 + a bit to allow for 9000 inside. I'm 1500 bytes at the customer edge for Internet. I'm also 1500 bytes at IXes. -- Richard

June 18, 2021

Re: Jumbo Frames

by Steve Savoy

Thanks for that input Jonathan! Steve From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jonathan Stewart Sent: Friday, June 18, 2021 2:16 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Jumbo Frames Hey Jamison, The consensus view is this: 1500 Bytes is the MTU of the internet, and MTU1500 has so much inertia that you or me or all this mailing list together could not change it. The sages also tell us that PMTUd--path MTU discovery--does not work with any reliability and thus does not work in reality. Things like NAT, firewalls and deep packet inspectors routinely break ICMP of all kinds. Most crushingly for an IX: there's no such thing as layer-2 MTU discovery. In the same L2 domain, all routers need to use the same MTU, or stuff will break (Jeremy pointed to one example of failing BGP message exchange). If I set my router to MTU1500, and you set yours to MTU9000, how would we ever know? This is a misconfiguration, so what could coordinate those values on an IX? Thus, we should all use MTU 1500. We could have a separate VLAN that's MTU 9000 where all the routers connected would set their interface to MTU 9000. The routers wouldn't have any MTU breakage over that L2 domain. SIX does this, and it seems the best and most rational way to allow MTU 9000 for those who want it. Finally, views do differ, i'm sure others have opinions that do not match mine. Cheers, Jonathan Jonathan Stewart Network Engineer LES.NET - AS18451 Desk: 1-204-666-6191 Mobile: 1-204-990-2120 130 Portage Avenue E Winnipeg, MB R3C 0A1 CANADA On Fri., 2021-06-18 1:09 p.m., Jamison Masters wrote: Hi all, We are migrating our connections to 10G, and I'm wondering if I should request jumbo frames. I'm trying for due diligence, and apologize if this is a rudimentary question. Nanog searches do not have clear recommendations, or maybe I did not search enough. My experience with jumbo frames indicates to me that I should be safe with 9000 byte frames, but there could be PMTU discovery and fragmentation issues during transit or on the receiving side. Would you or would you not enable 9K frames with IXP and ISP connections? I just do not have enough experience in this regard, so I am thankful for any thoughts here. My inclination is to go with 9K frames, yet I do not want to deal with ancillary issues that I cannot anticipate, discern, or troubleshoot - especially during a cut. Any experience from the group is appreciated. Thank you, Jamison Masters Verus Corporation jamison(a)veruscorp.com<mailto:jamison@veruscorp.com> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

June 18, 2021

Re: Jumbo Frames

by Jonathan Stewart

Hey Jamison, The consensus view is this: 1500 Bytes is the MTU of the internet, and MTU1500 has so much inertia that you or me or all this mailing list together could not change it. The sages also tell us that PMTUd--path MTU discovery--does not work with any reliability and thus does not work in reality. Things like NAT, firewalls and deep packet inspectors routinely break ICMP of all kinds. Most crushingly for an IX: there's no such thing as layer-2 MTU discovery. In the same L2 domain, all routers need to use the same MTU, or stuff will break (Jeremy pointed to one example of failing BGP message exchange). If I set my router to MTU1500, and you set yours to MTU9000, how would we ever know? This is a misconfiguration, so what could coordinate those values on an IX? Thus, we should all use MTU 1500. We could have a separate VLAN that's MTU 9000 where all the routers connected would set their interface to MTU 9000. The routers wouldn't have any MTU breakage over that L2 domain. SIX does this, and it seems the best and most rational way to allow MTU 9000 for those who want it. Finally, views do differ, i'm sure others have opinions that do not match mine. Cheers, Jonathan Jonathan Stewart Network Engineer LES.NET - AS18451 Desk: 1-204-666-6191 Mobile: 1-204-990-2120 130 Portage Avenue E Winnipeg, MB R3C 0A1 CANADA On Fri., 2021-06-18 1:09 p.m., Jamison Masters wrote: > > Hi all, > > We are migrating our connections to 10G, and I’m wondering if I should > request jumbo frames. > > I’m trying for due diligence, and apologize if this is a rudimentary > question. Nanog searches do not have clear recommendations, or maybe > I did not search enough. > > My experience with jumbo frames indicates to me that I should be safe > with 9000 byte frames, but there could be PMTU discovery and > fragmentation issues during transit or on the receiving side. > > Would you or would you not enable 9K frames with IXP and ISP > connections? I just do not have enough experience in this regard, so > I am thankful for any thoughts here. > > My inclination is to go with 9K frames, yet I do not want to deal with > ancillary issues that I cannot anticipate, discern, or troubleshoot – > especially during a cut. > > Any experience from the group is appreciated. > > Thank you, > > Jamison Masters > > Verus Corporation > > jamison(a)veruscorp.com <mailto:jamison@veruscorp.com> > > > ------------------------------------------------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> >

June 18, 2021

Re: Jumbo Frames

by Jeremy Lumby

The biggest thing I have run across is on an IX where everyone may be running a different MTU if you just set yours to 9K then your router will utilize all of it in it's BGP messaging. If the peer is not also set to 9K then things will get unstable once your router generates a BGP message that is larger than your peer's MTU. You would want to think about using something like "ip tcp adjust-mss 1460" to keep the BGP messaging smaller. Than 1500 while still supporting packets up to 9000 From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jamison Masters Sent: Friday, June 18, 2021 1:09 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Jumbo Frames Hi all, We are migrating our connections to 10G, and I'm wondering if I should request jumbo frames. I'm trying for due diligence, and apologize if this is a rudimentary question. Nanog searches do not have clear recommendations, or maybe I did not search enough. My experience with jumbo frames indicates to me that I should be safe with 9000 byte frames, but there could be PMTU discovery and fragmentation issues during transit or on the receiving side. Would you or would you not enable 9K frames with IXP and ISP connections? I just do not have enough experience in this regard, so I am thankful for any thoughts here. My inclination is to go with 9K frames, yet I do not want to deal with ancillary issues that I cannot anticipate, discern, or troubleshoot - especially during a cut. Any experience from the group is appreciated. Thank you, Jamison Masters Verus Corporation jamison(a)veruscorp.com ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 18, 2021

Jumbo Frames

by Jamison Masters

Hi all, We are migrating our connections to 10G, and I'm wondering if I should request jumbo frames. I'm trying for due diligence, and apologize if this is a rudimentary question. Nanog searches do not have clear recommendations, or maybe I did not search enough. My experience with jumbo frames indicates to me that I should be safe with 9000 byte frames, but there could be PMTU discovery and fragmentation issues during transit or on the receiving side. Would you or would you not enable 9K frames with IXP and ISP connections? I just do not have enough experience in this regard, so I am thankful for any thoughts here. My inclination is to go with 9K frames, yet I do not want to deal with ancillary issues that I cannot anticipate, discern, or troubleshoot - especially during a cut. Any experience from the group is appreciated. Thank you, Jamison Masters Verus Corporation jamison(a)veruscorp.com<mailto:jamison@veruscorp.com>

June 18, 2021

Re: Akamai 2x2x100G upgrade

by Jeremy Lumby

The switch config is complete. The new portchannel is 19 -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jay Hanke Sent: Wednesday, June 16, 2021 11:14 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Akamai 2x2x100G upgrade Akamai is upgrading from 1x1x100G LAG to 2x2x100G LAG Port Channel 1 MICE MAIN :: Ethernet3/3/1 [existing] MICE MAIN :: Ethernet3/26/1 [new] Existing IP Information AS20940 IPv4: 206.108.255.84/24 IPv6: 2001:504:27::51cc:0:1/64 Port Channel X <- needs switch ID MICE MAIN :: Ethernet6/8/1 [new] MICE MAIN :: Ethernet6/10/1 [new] New IP Information AS20940 IPv4: 206.108.255.85/24 IPv6: 2001:504:27::51cc:0:2/64 This email will serve as your LOA/CFA and has been filed with Cologix for cross connections to be ordered. We will follow up with an additional email as soon as optics have been installed and the ports have been provisioned. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

June 16, 2021

Akamai 2x2x100G upgrade

by Jay Hanke

Akamai is upgrading from 1x1x100G LAG to 2x2x100G LAG Port Channel 1 MICE MAIN :: Ethernet3/3/1 [existing] MICE MAIN :: Ethernet3/26/1 [new] Existing IP Information AS20940 IPv4: 206.108.255.84/24 IPv6: 2001:504:27::51cc:0:1/64 Port Channel X <- needs switch ID MICE MAIN :: Ethernet6/8/1 [new] MICE MAIN :: Ethernet6/10/1 [new] New IP Information AS20940 IPv4: 206.108.255.85/24 IPv6: 2001:504:27::51cc:0:2/64 This email will serve as your LOA/CFA and has been filed with Cologix for cross connections to be ordered. We will follow up with an additional email as soon as optics have been installed and the ports have been provisioned. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

June 16, 2021