- mice-discuss - lists.micemn.net

Upstream fiber work
by Jay Hanke 19 Feb '20

19 Feb '20

Arvig is conducting fiber maintenance on the circuit that feeds the SFN MICE remote. ETR 0500 2020-02-19 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

1 0

Google peering down just after 12:00 am
by Frank Bulk 12 Feb '20

12 Feb '20

Apparently Google has/had scheduled maintenance just after midnight? Frank

1 0

Global Net (AS395466) - Additional Prefix Advertisement
by Global Net NOC 11 Feb '20

11 Feb '20

MICEMN Members - We will be advertising an additional leased /21 prefix to our peers at MICEMN. The prefix is: 154.27.104.0/21 ARIN IRR has been updated. If any members require an LOA, please respond directly and I will procure. Thanks, Scott Reed Global Net NOC noc(a)theglobal.net Global Net Peering peering(a)theglobal.net

1 0

ARIN Policy Implementation Scheduled for the Week of 30 March 2020
by David Farmer 10 Feb '20

10 Feb '20

If your organization uses detailed reassignments in the ARIN Whois database for customers, you should pay close attention to this announcement. ---------- Forwarded message --------- From: ARIN <info(a)arin.net> Date: Mon, Feb 10, 2020 at 14:25 Subject: [arin-announce] Policy Implementation Scheduled for the Week of 30 March 2020 To: <arin-announce(a)arin.net> Over the last several years, the community has been discussing ARIN policy regarding how reallocations and reassignments are made to downstream organizations. As a result of these discussions, two new policies will be implemented in the coming weeks. These new policies may impact you, your downstream customers, and your automated SWIP scripts or email templates for detailed reassignments and reallocations. The changes to our systems required by these policies will be deployed during our next release cycle, scheduled for the week of 30 March 2020, as previously announced. When the community-driven policy changes ARIN 2017-12 and ARIN 2018-5 are implemented, organizations will be unable to create Points of Contact (POCs) or Organization IDs (Org IDs) for organizations other than their own. A recipient organization must create an Org ID and POC with ARIN before receiving a reassignment or reallocation. We have been working actively with community members to determine the best way to implement these policies because they have operational impacts for our customers. To assist our customers, we have published a detailed blog post that explains how these policies will change detailed reassignments and reallocations. https://teamarin.net/2020/02/07/two-new-policy-implementations-coming-what-… We encourage all of our customers who reassign/reallocate IP address space to their customers to review this blog post carefully, and to take advantage of the upcoming opportunity to test their automated processes prior to the implementation date. American Registry for Internet Numbers (ARIN) _______________________________________________ ARIN-Announce You are receiving this message because you are subscribed to the ARIN Announce Mailing List (ARIN-announce(a)arin.net) Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-announce Please contact info(a)arin.net if you experience any issues. -- =============================================== 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 ===============================================

1 0

All our BGP sessions to MICE down since just before 9 am
by Frank Bulk 07 Feb '20

07 Feb '20

Looks like Zayo transport issue, somewhere between northwest Iowa and Belle Plaine. Frank AS18883 AS53347

3 8

Please welcome KC Fiber to MICE!
by Jay Hanke 05 Feb '20

05 Feb '20

Name: KC Fiber Port: MN VoIP Remote Switch (1G) ASN: 11708 IPv4: 206.108.255.154/24 IPv6: 2001:504:27:0:0:2dbc::1/64 Peering Contact: peering(a)kcfiber.com Route Servers- YES BFD: No Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

2 1

DCN 100G Port Upgrade
by Jay Hanke 28 Jan '20

28 Jan '20

DCN will be adding a 100G port and keeping their existing 10G port. The new 100G port assignment is Ethernet3/17/1 on the main switch. The new port will use existing IP assignments (labeled Fargo) 206.108.255.60 2001:504:27:0:0:68AA::1 Please provide your Arista compatible optic to Cologix or to Jeremy for installation in the main switch. This email will serve as your LOA/CFA. Welcome Aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

1 0

Blackholing DoS traffic
by Frank Bulk 24 Jan '20

24 Jan '20

https://www.seattleix.net/blackholing Does MICE have an blackholng functionality equivalent to SIX? I was visiting with a DDoS mitigation vendor this morning and was curious if there was a way we could automatically mitigate DoS attack traffic coming from a MICE peer. Regards, Frank

12 17

Debian Mirrors
by Jay Hanke 17 Jan '20

17 Jan '20

Is anyone hosting Debian mirrors available over MICE? -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

5 9

Re: FW: Prefix Hijack: 206.108.255.0/24
by Frank Bulk 14 Jan '20

14 Jan '20

Thanks for sorting that out! Frank -----Original Message----- From: Brandon Mulligan <brandon(a)nocix.net> Sent: Tuesday, January 14, 2020 4:51 PM To: Frank Bulk <fbulk(a)mypremieronline.com>; MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Cc: noc(a)wholesaleinternet.net Subject: Re: FW: Prefix Hijack: 206.108.255.0/24 Frank + MICE, This was sent to a new customer by mistake who then sent it to a route collector. I did not detect this in Cogent's looking glass. This should be resolved now. Sorry for the alert and thanks for the notification! On 1/14/2020 3:37 PM, Frank Bulk wrote: > Not sure if it's valid, but Hurricane Electric says that MICE's /24 is being infringed upon by AS32097 (WholeSale Internet, Inc.) > > Copying WII. > > Frank > > -----Original Message----- > From: no-reply(a)he.net <no-reply(a)he.net> > Sent: Tuesday, January 14, 2020 3:26 PM > Subject: Prefix Hijack: 206.108.255.0/24 > > # Hijack Alert > > You are receiving this e-mail because one of your prefix registrations > matched this alarm. > > Prefix: 206.108.255.0/24 > Infringing AS: 32097 (via peer 23.139.160.84) > AS Path: 26073 32097 > When: 2020-01-14 21:16:50 UTC

1 0