- mice-discuss - lists.micemn.net

lost connection

by James Urwiller

I lost MICE through ZAYO again to belle plain around 15:18 CST. Anyone else? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com [image: stealth300]

May 14, 2019

Re: Please welcome Northland Communications to MICE!

by Doug McIntyre

On Tue, May 14, 2019 at 12:45:17PM -0500, Jay Hanke wrote: >Name: Northland Communications >Port: Ethernet 4 (SFN Albert Lea Remote) 10GE >ASN: 394907 >IPv4: 206.108.255.139/24 >IPv6: 2001:504:27:0:6:069b::1/64 >Peering Contact: noc(a)cltel.com >Route Servers- YES >BFD: NO > >Please note this company also does business under the CLTel name. > I've added them into the route servers now as well. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

May 14, 2019

Please welcome Northland Communications to MICE!

by Jay Hanke

Name: Northland Communications Port: Ethernet 4 (SFN Albert Lea Remote) 10GE ASN: 394907 IPv4: 206.108.255.139/24 IPv6: 2001:504:27:0:6:069b::1/64 Peering Contact: noc(a)cltel.com Route Servers- YES BFD: NO Please note this company also does business under the CLTel name. Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

May 14, 2019

MICE RS1 Spring Cleaning

by AnthonyAnderberg＠nuvera.net

As part of our spring cleaning effort this morning I removed the following unused neighbor entries on MICE Route Server 1 after verifying they were inactive. We’ll remove them from Route Server 2 next week. Removed these inactive former members, they’ve already been removed from the web site/member list: description "13573 - MDU Ethernet"; #Northstar/MDU Solutions neighbor 206.108.255.13 as 13573; neighbor 2001:504:27:0:0:3505::1 as 13573; description "135886 - Introvex Solutions Ltd"; neighbor 206.108.255.76 as 135886; neighbor 2001:504:27:0:2:12ce::1 as 135886; description "32314 - Future Wireless#2"; #Jag Wire Enterprises? neighbor 206.108.255.81 as 32314; neighbor 2001:504:27:0:0:7e3a::1 as 32314; description "33125 - Spiralight"; neighbor 206.108.255.12 as 33125; (No IP6 configured) description "3856 - Packet Clearing House/PCH.net"; neighbor 206.108.255.87 as 3856; neighbor 2001:504:27:0:0:0f10::1 as 3856; description "393846 - Unggoy"; neighbor 206.108.255.41 as 393846; neighbor 2001:504:27:0:6:0276::1 as 393846; description "42 - Packet Clearing House/PCH.net"; #Woodynet neighbor 206.108.255.86 as 42; neighbor 2001:504:27:0:0:2a::1 as 42; description "62512 - Sandwich.net"; neighbor 206.108.255.85 as 62512; neighbor 2001:504:27:0:0:f430::1 as 62512; description "8095 - NetValue Inc"; neighbor 206.108.255.28 as 8095; neighbor 2001:504:27:0:0:1f9f::1 as 8095; description "11055 - US Cable"; (was already commented out) Removed these entries that had been setup as temporary/migration neighbors, all three have other active neighbor statements: description "16851 #2 - NebraskaLink"; neighbor 206.108.255.71 as 16851; neighbor 2001:504:27:0:0:41d3::2 as 16851; description "36040- Google #2"; neighbor 206.108.255.34 as 36040; neighbor 2001:504:27:0:0:8cc8::2 as 36040; description "394330 - LTD Broadband"; neighbor 206.108.255.68 as 394330; neighbor 2001:504:27:0:6:045a::2 as 394330; Removed these entries because these members are only bilateral and/or don't use the route servers: description "32609 - CNS"; neighbor 206.108.255.50 as 32609; neighbor 2001:504:27:0:0:7F61::1 as 32609; description "12042 - Enventis - Consolidated Communications"; neighbor 206.108.255.18 as 12042; neighbor 2001:504:27:0:0:2F0A::1 as 12042; description "20115 - Charter Communications"; neighbor 206.108.255.64 as 20115; neighbor 2001:504:27:0:0:4E93::1 as 20115; description "20940 - Akamai CDN"; neighbor 206.108.255.84 as 20940; neighbor 2001:504:27:0:0:51cc::1 as 20940; description "21709 - Implex"; neighbor 206.108.255.5 as 21709; neighbor 2001:504:27:0:0:54cd::1 as 21709; description "22822 - Limelight Networks"; neighbor 206.108.255.43 as 22822; neighbor 2001:504:27:0:0:5926::1 as 22822; description "4181 - TDS"; neighbor 206.108.255.4 as 4181; neighbor 2001:504:27:0:0:1055::1 as 4181; [signature_195935134]

May 7, 2019

Facebook over IPv6

by Frank Bulk

DownDetector isn't showing anything significant, but we're seeing HTTPv6 access to http://www.facebook.com intermittently failing since 4:14 pm Frank root@nagios:/tmp# tcptraceroute6 www.facebook.com traceroute to star-mini.c10r.facebook.com (2a03:2880:f13a:83:face:b00c:0:25de) from 2607:fe28:0:1000::5, port 80, from port 34889, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.641 ms 0.220 ms 0.207 ms 2 2001:5f8:7f06:c::1 (2001:5f8:7f06:c::1) 0.175 ms 0.104 ms 0.167 ms 3 2001:5f8:7f06:e::2 (2001:5f8:7f06:e::2) 0.153 ms 0.150 ms 0.150 ms 4 2001:504:27::80a6:0:2 (2001:504:27::80a6:0:2) 16.859 ms 17.070 ms 7.540 ms 5 po102.psw02.msp1.tfbnw.net (2620:0:1cff:dead:bef0::395) 7.129 ms 7.082 ms 7.095 ms 6 po2.msw1af.01.msp1.tfbnw.net (2a03:2880:f03a:ffff::3f) 7.033 ms 7.041 ms 7.057 ms 7 edge-star-mini6-shv-01-msp1.facebook.com (2a03:2880:f13a:83:face:b00c:0:25de) 6.940 ms [open] 6.958 ms 6.920 ms root@nagios:/tmp#

May 6, 2019

New Compudyne MICE Remote Switches

by Jay Hanke

Compudyne will be deploying new remote switches in their 511 space and in their Duluth data center via a new 20G LAG to the main switch. Port: Ethernet 4/34 Port: Ethernet 5/34 511 Switch IPv4: 206.108.255.230/24 IPv6: 2001:504:27:0:0:b7f8::230/64 Duluth Switch IPv4: 206.108.255.231/24 IPv6: 2001:504:27:0:0:b7f8::231/64 Their existing connection via the MN VoIP remote will move to the new switches with no IP changes. Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

May 3, 2019

Arista & Pure Storage CEO Roundtable Tuesday, May 7th 12pm - 4pm

by John McLaughlin

Hello MICE Members: Please join us next week for this unique opportunity to meet two of Silicon Valley’s top CEO’s. Please use the link below to register. arista-pure-storage <https://events.arista.com/arista-pure-storage> John McLaughlin 612-816-9024 North Central Sales jmclaughlin(a)arista.com

May 2, 2019

618G for MICE!

by AnthonyAnderberg＠nuvera.net

Our combined in/out traffic last night peaked at 618G, just 5 months after we peaked at 500G in/out for the first time! Looking at the weathermap it appears most everyone’s traffic was up some during the peak - likely because of a rainy cool spring evening here in the Midwest keeping everyone indoors. [cid:image001.png@01D5001B.FE6C3900] Thanks for everyone’s efforts, anthony [signature_1565179850]

May 1, 2019

Re: Brocade MICE Client Port config

by Jay Hanke

On Tue, Apr 30, 2019 at 6:53 PM Brandon Mulligan <brandon(a)kcix.net> wrote: > > The SIX guides work well. Its how we configured all our MLXe/XMR edges on Wholesale. Yes, good stuff.

May 1, 2019

Re: Brocade MICE Client Port config

by Jay Hanke

> The website currently only shows the configuration for the _MICE_ side, > for reference. We link to the AMS-IX Config Guide for advice on > configuring the participant's side. I see that link has gone stale, and > I've updated it. Right, the member side examples might be more useful to the members. It might be worth getting them posted up on the MICE website directly. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

May 1, 2019