- mice-discuss - lists.micemn.net

Please welcome x6c to MICE!

by Jeremy Lumby

Name: x6c inc Switch: NOCIX Ports: E 5/18 ASN: 46733 IPv4: 206.108.255.235/24 IPv6: 2001:504:27:0:0:B68D::1/64 Peering Contact: support(a)x6c.co Route Servers: YES 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

Sept. 23, 2024

Please welcome Essentia Health to MICE!

by Jeremy Lumby

Name: Essentia Health Switch: MICE Core 511 Ports: E 4/34 & 4/40 have been seaparated out of the portchannel so that they can connect redundant routers ASN: 3789 IPv4: Adding 206.108.255.234 to the existing IPs IPv6: Adding 2001:504:27::ecd:0:2 to the existing IPs Peering Contact: nickolas.stevermer(a)essentiahealth.org Route Servers: Partial 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

Sept. 18, 2024

Please welcome Netflix to MICE!

by Jeremy Lumby

Name: Netflix Switch: MICE Core 511 Ports: adding E3/27/1 to portchannel 2 and adding E 6/20/1 to portchannel 3 for a total of 2x2x100G ASN: 2906 IPv4: All IP info remains the same, this is a 2x100G port addition IPv6: Peering Contact: peering(a)netflix.com Route Servers: 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

Sept. 13, 2024

Please welcome Essentia Health to MICE!

by Jeremy Lumby

Name: Essentia Health Switch: MICE Core 511 Ports: E 4/34 & 4/40 in portchannel 28 for a total of 2x10G ASN: 3789 IPv4: All IP info remains the same, this is a switch move, and port addition. IPv6: Peering Contact: nickolas.stevermer(a)essentiahealth.org Route Servers: Partial 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

Sept. 11, 2024

Fwd: [arin-announce] Reminder of Upcoming Deadline for ARIN’s Multifactor Authentication (MFA) Enforcement for ARIN Online

by David Farmer

If you still need to enable MFA on your ARIN Online Account, DO IT NOW! More than 15,000 ARIN Online Accounts have yet to enable MFA, which is nuts! Thanks. ---------- Forwarded message --------- From: ARIN <info(a)arin.net> Date: Mon, Sep 9, 2024 at 11:25 AM Subject: [arin-announce] Reminder of Upcoming Deadline for ARIN’s Multifactor Authentication (MFA) Enforcement for ARIN Online To: <arin-announce(a)arin.net> On 7 October 2024, ARIN will lock all remaining ARIN Online accounts that have not enabled multifactor authentication (MFA). As of 1 February 2023, ARIN requires MFA on all new ARIN Online accounts. Users with accounts created before February 2023 were notified and encouraged to log in at their earliest opportunity, where they would be prompted to set up MFA. This step was taken to provide stronger security for the registry, reduce the risk of fraud, and increase confidence in the integrity of their ARIN resources. On 17 July, we announced that ARIN was continuing to take steps to secure the registry by enforcing MFA. We engaged in direct communications with 19,853 account holders linked to organizations with direct allocations, detailed reassignments, and reallocations who had not yet enabled MFA on their accounts. These users were notified that they needed to set up MFA within 60 days or their accounts would be locked, As of 4 September 2024, 15,593 accounts have not completed MFA setup. We are extending this deadline by two weeks to allow more time for account holders to enable MFA on existing accounts. We strongly encourage ARIN Online account holders who have not set up MFA to do so before the 7 October deadline. Users with locked accounts can contact Registration Services during ARIN operating hours, 7:00 AM to 7:00 PM ET Monday through Friday, to unlock and set up MFA and regain access to ARIN Online. ARIN relies on the support of its customers to ensure the accuracy and security of the registry. We rely on all our customers to follow best practices for account security and to report any suspicious activity to us immediately. Regards, John Curran President and CEO American Registry for Internet Numbers (ARIN) --------- Helpful Resources: Need help setting up your MFA? Visit https://www.arin.net/MFA to get started. You’ll find guides on enabling MFA via an authenticator application, SMS, or security key hardware. We also provide information on how to receive and save your MFA recovery codes, as well as what to do if you’ve lost access to your authenticator app, SMS phone number, or security key. -- =============================================== 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 ===============================================

Sept. 9, 2024

Re: [EXT]: Re: [MICE-DISCUSS] [EXTERNAL] - Re: [MICE-DISCUSS] Odd AWS transfer issue

by Danny Meister

Sept. 7, 2024

Re: [EXTERNAL] - Re: [MICE-DISCUSS] Odd AWS transfer issue

by Miles McCredie

The graph definitely looks better. [cid:image002.png@01DB0083.B32035F0] Danny, Isaiah - Are the downloads back to normal? [http://images.midcocomm.com/ES_MidcoLogo.png] Miles McCredie Principal Network Engineer II-Core IP Office: 6052755192 Miles.McCredie(a)midco.com Midco.com Let's go beyond. From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Friday, September 6, 2024 2:40 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [EXTERNAL] - Re: [MICE-DISCUSS] Odd AWS transfer issue CAUTION: This email originated from outside of MIDCO. Do not click links or open attachments unless you recognize the sender and know the content is safe. I have been informed that Amazon has corrected the issue, and things are looking good now. Is everything testing out OK now? From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> On Behalf Of Danny Meister Sent: Friday, September 6, 2024 11:41 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: [MICE-DISCUSS] Odd AWS transfer issue Good Afternoon, I've been trying to track down a strange packet loss issue when a customer of mine is downloading files from S3 in the east region. We peer with AWS via MICE and traffic to east routes via MICE. Could any of you folks peered with AWS via MICE try downloading this file a bunch of times and reports the results? http://ofw-atomic-data-test-region-us-east-1.s3-website-us-east-1.amazonaws… Basically, we see fast transfers maybe 80% of the time and then it will be slow, like sub 1Mb slow (we can replicate the issue with iperf to an EC2 instance also). Captures show lots of retransmits, etc during a slow transfer. If I shut down my AWS peering the problem goes away. I was able to test from another client of mine connected to Arvig and I'm pretty sure I can replicate the issue from there. So, I'm not convinced it's just me. On the other hand, if there is a problem, I'm surprised no one else has noticed! Thanks! Danny Meister Infrastructure Engineer 612.466.2071 | DMeister(a)atomicdata.com<mailto:DMeister@atomicdata.com> [cid:image003.png@01DB0083.B32035F0]<https://www.atomicdata.com/?utm_campaign=signature&amp;utm_source=Email…> 250 Marquette Avenue South | Minneapolis, MN | 55401 atomicdata.com<https://www.atomicdata.com/?utm_campaign=signature&utm_source=EmailSign…> | Services<https://www.atomicdata.com/services?utm_campaign=Signature&utm_source=Email> | Blog<https://www.atomicdata.com/blog?utm_campaign=Signature&utm_source=Email> Atomic Data Welcomes Chris Heim as CEO<https://www.atomicdata.com/atomic-data-welcomes-chris-heim-as-ceo/?utm_sour…> ________________________________ 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

Sept. 6, 2024

Re: Odd AWS transfer issue

by Jeremy Lumby

I have been informed that Amazon has corrected the issue, and things are looking good now. Is everything testing out OK now? From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > On Behalf Of Danny Meister Sent: Friday, September 6, 2024 11:41 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: [MICE-DISCUSS] Odd AWS transfer issue Good Afternoon, I've been trying to track down a strange packet loss issue when a customer of mine is downloading files from S3 in the east region. We peer with AWS via MICE and traffic to east routes via MICE. Could any of you folks peered with AWS via MICE try downloading this file a bunch of times and reports the results? http://ofw-atomic-data-test-region-us-east-1.s3-website-us-east-1.amazonaws. com/empty_test_file_50M.txt Basically, we see fast transfers maybe 80% of the time and then it will be slow, like sub 1Mb slow (we can replicate the issue with iperf to an EC2 instance also). Captures show lots of retransmits, etc during a slow transfer. If I shut down my AWS peering the problem goes away. I was able to test from another client of mine connected to Arvig and I'm pretty sure I can replicate the issue from there. So, I'm not convinced it's just me. On the other hand, if there is a problem, I'm surprised no one else has noticed! Thanks! Danny Meister Infrastructure Engineer 612.466.2071 | DMeister(a)atomicdata.com <mailto:DMeister@atomicdata.com> <https://www.atomicdata.com/?utm_campaign=signature&amp;amp;utm_source=E mailSignature> 250 Marquette Avenue South | Minneapolis, MN | 55401 <https://www.atomicdata.com/?utm_campaign=signature&amp;utm_source=Email Signature> atomicdata.com | <https://www.atomicdata.com/services?utm_campaign=Signature&utm_source=E mail> Services | <https://www.atomicdata.com/blog?utm_campaign=Signature&utm_source=Email > Blog <https://www.atomicdata.com/atomic-data-welcomes-chris-heim-as-ceo/?utm_sour ce=EmailSignature> Atomic Data Welcomes Chris Heim as CEO _____ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> &A=1

Sept. 6, 2024

Re: [EXTERNAL] - [MICE-DISCUSS] Odd AWS transfer issue

by Chris Wopat

That is such a high error rate that we should perhaps just shut the port down so the traffic routes elsewhere, properly. Based on the graph it appears to be a failing optic - could perhaps be confirmed if Cacti is trending TX/RX power and TX Bias. --Chris >

Sept. 6, 2024

Re: [EXTERNAL] - [MICE-DISCUSS] Odd AWS transfer issue

by Jay Hanke

Jeremy caught the issue and reached out to Amazon a couple of weeks ago regarding the areas. It might help for those having issues to reach out to Amazon directly to knock it loose on their side. On Fri, Sep 6, 2024, 12:36 PM Isaiah Olson <iolson(a)paulbunyan.net> wrote: > It looks like Amazon’s port Ethernet6/1/1 on the MICE Core switch has some > pretty significant errors. > > > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Miles > McCredie > *Sent:* Friday, September 06, 2024 12:12 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* Re: [MICE-DISCUSS] [EXTERNAL] - [MICE-DISCUSS] Odd AWS > transfer issue > > > > Maybe someone could check for errors on the MICE ports for Atomic Data and > Amazon. > > > > Assuming the MICE ports are clean, it is probably worth following up with > the Amazon NOC, peering-to(a)amazon.com. They did some work on their > Minneapolis peering routers recently though I’m not sure what they were > doing. > > > > > > > > [image: Image removed by sender.] > > *Miles McCredie * > Principal Network Engineer II-Core IP > > Office: 6052755192 > Miles.McCredie(a)midco.com > > *Midco.com* > > Let's go beyond. > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Danny > Meister > *Sent:* Friday, September 6, 2024 11:41 AM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [EXTERNAL] - [MICE-DISCUSS] Odd AWS transfer issue > > > > *CAUTION:* This email originated from outside of *MIDCO*. > *Do not click links or open attachments unless you recognize the sender > and know the content is safe.* > > Good Afternoon, > > > > I've been trying to track down a strange packet loss issue when a customer > of mine is downloading files from S3 in the east region. We peer with AWS > via MICE and traffic to east routes via MICE. > > > > Could any of you folks peered with AWS via MICE try downloading this file > a bunch of times and reports the results? > > > > > http://ofw-atomic-data-test-region-us-east-1.s3-website-us-east-1.amazonaws… > > > > > Basically, we see fast transfers maybe 80% of the time and then it will be > slow, like sub 1Mb slow (we can replicate the issue with iperf to an EC2 > instance also). Captures show lots of retransmits, etc during a slow > transfer. If I shut down my AWS peering the problem goes away. I was able > to test from another client of mine connected to Arvig and I'm pretty sure > I can replicate the issue from there. So, I'm not convinced it's just me. > On the other hand, if there is a problem, I'm surprised no one else has > noticed! > > > > Thanks! > > *Danny Meister * > > Infrastructure Engineer > > 612.466.2071 | DMeister(a)atomicdata.com > > [image: Logo] > <https://www.atomicdata.com/?utm_campaign=signature&amp;utm_source=Email…> > > 250 Marquette Avenue > <https://www.google.com/maps/search/250+Marquette+Avenue?entry=gmail&source=g> > South | Minneapolis, MN | 55401 > > *atomicdata.com* > <https://www.atomicdata.com/?utm_campaign=signature&utm_source=EmailSign…> > | *Services* > <https://www.atomicdata.com/services?utm_campaign=Signature&utm_source=Email> > | *Blog* > <https://www.atomicdata.com/blog?utm_campaign=Signature&utm_source=Email> > *Atomic Data Welcomes Chris Heim as CEO* > <https://www.atomicdata.com/atomic-data-welcomes-chris-heim-as-ceo/?utm_sour…> > > > > > ------------------------------ > > 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 > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Sept. 6, 2024