February 2017 - mice-discuss - lists.micemn.net

Additional Google Ports

by Jason Hanke

Please allocate the following ports to Google. They can be added to the existing LAG. xe-2/0/29 xe-0/1/3 Google will move to 100G as soon as it is available. -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Feb. 10, 2017

Re: Unknown Unicast

by Jeremy Lumby

It is looking good now -----Original Message----- From: Seth Von Helmst [mailto:svonhelmst@nextera.net] Sent: Wednesday, February 08, 2017 8:54 AM To: Jeremy Lumby; MICE Discuss Cc: peering; peering(a)google.com Subject: RE: [MICE-DISCUSS] Unknown Unicast Nextera has resolved the issue and things should now be normalized please let me know if you see differently. Thank you, Seth -----Original Message----- From: Jeremy Lumby [mailto:jlumby@mnvoip.com] Sent: Tuesday, February 7, 2017 11:27 PM To: MICE Discuss Cc: Seth Von Helmst; peering; peering(a)google.com Subject: RE: [MICE-DISCUSS] Unknown Unicast I just did a quick packet capture, and it is all Google traffic headed for Nextera. Nextera had fixed their issue around 3 this past afternoon, however it looks like it has re-occurred. The issue is two fold. Nextera's interface has an issue, and has gone down. Google's BGP session with them is stuck in established, so they continue to send traffic towards a down interface. Since the MAC of Nextera's interface has timed out of MICE's switches, the traffic is being flooded to all ports. I am adding Nextera, and Google to this. Jeremy -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jason Hanke Sent: Tuesday, February 07, 2017 10:44 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Unknown Unicast I'm seeing a lot of what I think is unknown unicast on my remote. Looks like its coming from the main switch. Is this still from the Nextera issue today? -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Feb. 8, 2017

Re: Unknown Unicast

by Seth Von Helmst

Nextera has resolved the issue and things should now be normalized please let me know if you see differently. Thank you, Seth -----Original Message----- From: Jeremy Lumby [mailto:jlumby@mnvoip.com] Sent: Tuesday, February 7, 2017 11:27 PM To: MICE Discuss Cc: Seth Von Helmst; peering; peering(a)google.com Subject: RE: [MICE-DISCUSS] Unknown Unicast I just did a quick packet capture, and it is all Google traffic headed for Nextera. Nextera had fixed their issue around 3 this past afternoon, however it looks like it has re-occurred. The issue is two fold. Nextera's interface has an issue, and has gone down. Google's BGP session with them is stuck in established, so they continue to send traffic towards a down interface. Since the MAC of Nextera's interface has timed out of MICE's switches, the traffic is being flooded to all ports. I am adding Nextera, and Google to this. Jeremy -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jason Hanke Sent: Tuesday, February 07, 2017 10:44 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Unknown Unicast I'm seeing a lot of what I think is unknown unicast on my remote. Looks like its coming from the main switch. Is this still from the Nextera issue today? -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Feb. 8, 2017

Re: Unknown Unicast

by Jeremy Lumby

I just did a quick packet capture, and it is all Google traffic headed for Nextera. Nextera had fixed their issue around 3 this past afternoon, however it looks like it has re-occurred. The issue is two fold. Nextera's interface has an issue, and has gone down. Google's BGP session with them is stuck in established, so they continue to send traffic towards a down interface. Since the MAC of Nextera's interface has timed out of MICE's switches, the traffic is being flooded to all ports. I am adding Nextera, and Google to this. Jeremy -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jason Hanke Sent: Tuesday, February 07, 2017 10:44 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Unknown Unicast I'm seeing a lot of what I think is unknown unicast on my remote. Looks like its coming from the main switch. Is this still from the Nextera issue today? -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Feb. 8, 2017

Unknown Unicast

by Jason Hanke

I'm seeing a lot of what I think is unknown unicast on my remote. Looks like its coming from the main switch. Is this still from the Nextera issue today? -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Feb. 8, 2017

MICE Remote Moves

by Jason Hanke

Are there any members planning to move to a remote switch in the next 6 months? We are running short on ports to accommodate growth until the new fabric is installed. -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Feb. 8, 2017

8am 10x Route Server Traffic Increase?

by Matthew Beckwell

Noticed at 8am this morning, traffic to the MICE route servers has gone from it's usual ~60k bi-directional traffic, to a sustained 800k-1000k of mostly traffic out to both route server ports. Might be nothing. Might be something (misconfigured?) ~Matthew

Feb. 7, 2017

Re: Please welcome Limelight Networks to MICE!

by Doug McIntyre

On Mon, Feb 06, 2017 at 09:25:13AM -0600, Jason Hanke wrote: > Name: Limelight Networks > ASN: 22822 > IPv4: 206.108.255.43/24 > IPv6: 2001:504:27:0:0:5926::1/64 > Port: Main Switch xe-2/0/1 (Single Member LAG) > Contact: peering-team(a)llnw.com > BFD: NO > Route Server: NO > > Limelight will upgrade to 2x10G LAG as soon as the new switch is available. Okay, route servers setup to talk to them, and ae16.0 has been created on core-sw1 to bind xe-2/0/1 into a LAG running LACP for when they are ready in the future. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Feb. 6, 2017

Please welcome Limelight Networks to MICE!

by Jason Hanke

Name: Limelight Networks ASN: 22822 IPv4: 206.108.255.43/24 IPv6: 2001:504:27:0:0:5926::1/64 Port: Main Switch xe-2/0/1 (Single Member LAG) Contact: peering-team(a)llnw.com BFD: NO Route Server: NO Limelight will upgrade to 2x10G LAG as soon as the new switch is available. Welcome aboard! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Feb. 6, 2017

Compudyne (AS47096) Maintenance 2017-02-06

by Ryan Nelson

Hi All, FYI, On Monday morning (2017-02-06) the prefixes and peering sessions for Compduyne (AS47096) will be turned off for maintenance at 4:00am CST. They should be back online by 7:00am CST. Ryan Nelson | Network Services Architect Compudyne | 306 W Michigan Street - Suite 200 | Duluth, MN 55802 rnelson(a)compudyne.com<mailto:rnelson@compudyne.com> | 218.336.2220 | compudyne.com<http://www.compudyne.com/> Duluth | Hibbing | Saint Paul | Marquette | Houghton | Anchorage ________________________________ [cid:image002.png@01D0BA36.584BB020]

Feb. 3, 2017