- mice-discuss - lists.micemn.net

LTD Broadband 2nd port
by Jason Hanke Aug. 1, 2016

Aug. 1, 2016

LTD Broadband is adding a second MICE connection on the main switch. Their connection on the NP Remote switch will remain. Port: xe-2/0/4 IPv4: 206.108.255.42/24 IPv6: 2001:504:27:0:6:045A::2/64 ASN: 394330 Contact: corey.hauer(a)ltdbroadband.com They will need route server config for this port as well. These ports will NOT be in a LAG group. Welcome Aboard (again)! -- 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

2 1

State of MN DNS Issues
by Richard Laager July 20, 2016

July 20, 2016

FYI: state.mn.us DNS has broken DNSSEC and broken IPv6. I called yesterday, and they were aware of the DNSSEC issue. http://dnsviz.net/d/state.mn.us/dnssec/ -- Richard

3 3

Fwd: [JPTECHS] Fwd: [MICE-DISCUSS] State of MN DNS Issues
by David Farmer July 19, 2016

July 19, 2016

I forwarded this off to the guys at the state, here is a response. Thanks ---------- Forwarded message ---------- From: Reilly, Russ (MNIT) <russ.reilly(a)state.mn.us> Date: Tue, Jul 19, 2016 at 9:19 AM Subject: Re: Fwd: [MICE-DISCUSS] State of MN DNS Issues Thanks, we are aware of some complaints and working the issue. Something possibly related to how IPv6 was enable on the Infoblox and the various addresses. Comcast was broke Saturday and we got that fixed so it seems there are just oddities in various resolvers we are working through this with Infoblox. *Russ Reilly* | Network Support, network Support Manager MN.IT Services, State of Minnesota 651-201-1022 (w) *| * russ.reilly(a)state.mn.us *[image: Title: MN.IT Services logo - Description: MN.IT Services logo]* <http://www.mn.gov/oet> Information Technology for Minnesota Government *|* mn.gov/mnit <http://www.mn.gov/oet> Begin forwarded message: *From:* Doug McIntyre <merlyn(a)IPHOUSE.NET <merlyn(a)iphouse.net>> *Date:* July 19, 2016 at 08:51:27 CDT *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET <MICE-DISCUSS(a)lists.iphouse.net> *Subject:* *Re: [MICE-DISCUSS] State of MN DNS Issues* *Reply-To:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <MICE-DISCUSS(a)lists.iphouse.net>> On Tue, Jul 19, 2016 at 03:42:13AM -0500, Richard Laager wrote: FYI: state.mn.us DNS has broken DNSSEC and broken IPv6. I called yesterday, and they were aware of the DNSSEC issue. I had to push out the early beta BIND 9.11 out to production so I could use the new Negative Trust anchor option for them on my frontline resolvers. rndc nta state.mn.us [view] I think only BIND based resolvers thought it was an error though. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades -- =============================================== 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

Good news from Akamai (Finally)
by DeLong, Owen July 13, 2016

July 13, 2016

We have resolved the router issue and we are now delivering almost 8 Gbps to MICE. I expect this will continue to increase as things stabilize over the coming days. Please let me know if you have any questions. Also, in case you missed the first few memos… WE NO LONGER PEER WITH ROUTE SERVERS at MICE. If you want Akamai Traffic, you must set up bilateral peering with us. Send email to peering(a)akamai.com If you send email to peering(a)akamai.com and do not receive a response within 48 hours, please resend your email and CC owen(a)akamai.com. We will respond to peering requests on a timely basis and we have an open peering policy. Owen

2 2

Akamai @ MICE
by DeLong, Owen July 12, 2016

July 12, 2016

Among the multitude of problems that have plagued this process, we have discovered yet another one. This time, it’s not actually our fault. It seems that the nifty new Juniper we deployed there is suffering from a hardware failure in the form of a memory failure which is causing a number of odd behaviors (such as forwarding packets in ways that don’t agree with the forwarding table). We are working to resolve this latest issue as quickly as possible and will continue to work to bring this site back up to full capacity as soon as possible. We apologize (again) for any inconvenience. Owen

1 0

Slack
by Jason Hanke July 1, 2016

July 1, 2016

Does anyone on the list use Slack? Would a MICE Slack channel be useful? -- 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

4 6

Remote Switch Procedures
by Richard Laager June 28, 2016

June 28, 2016

Does the new "Remote Switch" section on the technical page match everyone's understanding of the remote switch procedure and obligations? If not, please suggest specific corrections and I'll get right on it. http://micemn.net/technical.html I'm not sure if we have a formal agreement document. If I get one, I'll update accordingly, and also upload the document itself. -- Richard

1 0

MICE UG 18 - Minutes
by Shaun Carlson June 27, 2016

June 27, 2016

Please see attached minutes; please let me know if there are any corrections. Thanks! s *Shaun Carlson*Senior Manager of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com

2 2

Akamai
by DeLong, Owen June 22, 2016

June 22, 2016

MICE Participants, We’ve had some reports of peering(a)akamai.com<mailto:peering@akamai.com> email getting lost. We are looking into those reports. If you have not received a reply to your email, please resend it one more time and CC owen(a)akamai.com<mailto:owen@akamai.com>. I will personally make sure to get your peering session established as well as add you to the list of missing emails to be investigated. If you were peering with us on the route servers and have not yet requested bilateral peering with us on the exchange, please also send an email to peering(a)akamai.com<mailto:peering@akamai.com> and CC owen(a)akamai.com<mailto:owen@akamai.com> so that we can get a session created. We are no longer peering with the route servers at MICE, so if you want to receive traffic from us over MICE, you must configure a bilateral peering connection. We apologize for any inconvenience and we are working to restore full service as quickly as possible. We currently have limited capacity up and running in Minneapolis and will be installing additional capacity in the coming weeks. Our current target date for full service is July 15. Owen

1 0

UG 20 Minutes
by Shaun Carlson June 22, 2016

June 22, 2016

Please see attached. REMINDER: Nominations for the open board position after UG 21 are now OPEN I will follow up with the final copies of the approved bylaws when I get home later this week. s *Shaun Carlson*Director of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com

1 0