November 2019 - mice-discuss - lists.micemn.net

Re: Google Issues?

by David Farmer

Looks like it came back just before 04:00. On Mon, Nov 18, 2019 at 8:35 PM Jeff Dahna <jeff.dahna(a)windommn.com> wrote: > Apparently it is a fiber cut on Level3 as per previous message. > -- =============================================== 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 ===============================================

Nov. 19, 2019

Re: Google Issues?

by Richard Laager

On 11/18/19 8:30 PM, Nathan Beard wrote: > Google peering sessions via MICE have been down for nearly 8 hours at > this point for multiple customers including Stellar Association. For networks that have Google caches, are you advertising only customer routes to them, or also advertising peer routes? The latter supposedly enables peer-to-peer cache fill, which may be helpful, especially in times like this. https://support.google.com/interconnect/answer/7658603 > What should I advertise to the GGC node? > You should advertise all your user prefixes. If you have peers and > downstream customers, you may advertise their prefixes too. https://support.google.com/interconnect/answer/7658593 > Can GGC nodes cache-fill from other GGC nodes? > Yes. We refer to this as peer-to-peer cache-fill. It can lead to > substantial improvements in resilience, and reduction in transit or > AS15169 peering traffic. > > To enable peer-to-peer traffic, the IP prefix of the GGC servers must > be advertised to all GGC nodes that you want to be candidates to be > cache-fill sources. These other nodes can be in your network or nodes > hosted by your peers. > > It is possible for cache-fill traffic to flow in both directions > between two nodes, or between two ASNs. -- Richard

Nov. 19, 2019

Re: Google Issues?

by Jeff Dahna

Apparently it is a fiber cut on Level3 as per previous message.

Nov. 19, 2019

Google Issues?

by Nathan Beard

All, Google peering sessions via MICE have been down for nearly 8 hours at this point for multiple customers including Stellar Association. Is anybody aware of an issue? I don't recall seeing an update for any work being completed but it's possible that I missed something... *Nathan Beard* *7Sigma Systems, Inc.* Network Engineer (218) 820-7636 www.7sigma.com

Nov. 19, 2019

Re: MICE Limelight Upgrade/Route Server addition

by Richard Laager

On 11/18/19 7:42 PM, Jay Hanke wrote: > Limelight is moving from their existing 2x10G LAG to 1x100G LAG on > main switch port 3/15/1. The existing 10G ports will be vacated. This > move was competed this afternoon. > > Limelight is also adding an additional 100G port to the MN VoIP remote > switch with an additional IP assignment. > > Name: Limelight (New additional) > Port: MN VoIP Port 2 (100G Switch) > ASN: 22882 > IPv4: 206.108.255.151 > IPv6: 2001:504:27:0:0:5926::2 > > Limelight has also requested RS sessions for both of their IP assignments. Are they doing full routes with the route servers, or just partial? That is, their website Route Server value is currently "No". Does it move to "Yes" or "Partial"? -- Richard

Nov. 19, 2019

MICE Limelight Upgrade/Route Server addition

by Jay Hanke

Limelight is moving from their existing 2x10G LAG to 1x100G LAG on main switch port 3/15/1. The existing 10G ports will be vacated. This move was competed this afternoon. Limelight is also adding an additional 100G port to the MN VoIP remote switch with an additional IP assignment. Name: Limelight (New additional) Port: MN VoIP Port 2 (100G Switch) ASN: 22882 IPv4: 206.108.255.151 IPv6: 2001:504:27:0:0:5926::2 Limelight has also requested RS sessions for both of their IP assignments. The following Limelight IPs need RS sessions created or verified IPv4: 206.108.255.43 IPv6: 2001:504:27:0:0:5926::1 Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 19, 2019

Re: Google

by Jeff Dahna

ETA= Estimated Time of Arrival. It is going to be awhile before it is restored. ETR= Estimated Time of Restoration

Nov. 18, 2019

Re: Google

by Dean Bahls

Ahh, thanks for setting me straight. That's actually pretty impressive if they can get it fixed that quickly. Dean -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Mike Johnston Sent: Monday, November 18, 2019 3:32 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Google On 2019-11-18 15:23, Dean Bahls wrote: > 23:00 ETA is not good. The ETA was stated as GMT, not local time. 23:00 GMT is 17:00 (5:00pm) local time.

Nov. 18, 2019

Re: Google

by Mike Johnston

On 2019-11-18 15:23, Dean Bahls wrote: > 23:00 ETA is not good. The ETA was stated as GMT, not local time. 23:00 GMT is 17:00 (5:00pm) local time.

Nov. 18, 2019

Re: Google

by Dean Bahls

I wonder if Zayo cut it…. JUST KIDDING! 😊 23:00 ETA is not good. I’m hearing some pretty ugly stories of folks suffering with this cut. Tells you how much folks rely on MICE nowadays!! Dean From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Andrew Hoyos Sent: Monday, November 18, 2019 3:18 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Google The latest update we had from Level3 (hey, look, a non Zayo related fiber issue, haha!) *** CASCADED EXTERNAL NOTES 18-Nov-2019 20:39:54 GMT From CASE: 17573224 - Event The Transport NOC reports that light level testing indicates a potential fault 13.8 kilometers from the testing site. The Outside Plant Engineer (OSPE) was engaged, provided the test results, and requested to assist with locating the exact point of failure. The OSPE has dispatched Field Operations personnel to the approximate location of the fault to begin searching for the physical damage point. As a precaution, construction teams have been engaged and dispatched to the approximate location of the damage. An ETA of approximately 23:00 GMT has been provided for the construction teams. On Nov 18, 2019, at 3:11 PM, Jeremy Schmeichel <Jeremy.Schmeichel(a)VASTBROADBAND.COM <mailto:Jeremy.Schmeichel@VASTBROADBAND.COM> > wrote: I’m glad someone asked, because I was wondering why our peer went down. Makes sense. From: MICE Discuss < <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Andrew Hoyos Sent: Monday, November 18, 2019 2:04 PM To: <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Google We lost some Level3 circuits at the same time as their peer dropped, due to a fiber cut in Wisconsin (near Dousman, WI). I’m 99.99% sure Google optical network rides that fiber from Chicago -> MSP, which implies they seem to be single homed, and backhauled to Chicago. On Nov 18, 2019, at 3:01 PM, Dean Bahls < <mailto:dean.bahls@COOPERATIVE-NETWORKS.COM> dean.bahls(a)COOPERATIVE-NETWORKS.COM> wrote: Any word on what’s going on at Google? I’m guessing someone had a bad day. Dean Dean Bahls Network Services Manager | Cooperative Network Services, LLC 14 Main St SW | PO Box J | Menahga, MN 56464 218.346.3635 (Direct) | 218.564.3000 (Main Office) <mailto:dean.bahls@cooperative-networks.com> dean.bahls(a)cooperative-networks.com <image003.jpg> _____ 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 _____ 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 CONFIDENTIAL: This email and any files transmitted with it are confidential and intended solely for the use of Vast Broadband/NTS and to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. CONFIDENTIAL: This email and any files transmitted with it are confidential and intended solely for the use of Vast Broadband/NTS and to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. _____ 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 _____ 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

Nov. 18, 2019