- mice-discuss - lists.micemn.net

Agenda Items - Last Call
by Shaun Carlson July 22, 2014

July 22, 2014

All, Please send any additional agenda (business, technical or discussion) items you may have. I plan to have the Agenda out this afternoon for Thursday's meeting. Also, one more quick reminder. If you haven't responded yet, please let me know your AS and number of people attending. Thanks! s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

5 4

IPv6 neighbor solicitation at the exchange
by James Stahr July 21, 2014

July 21, 2014

First off, Did anyone make any changes on 07/15/2014 around 08:00? The reason is that I think I've resolved an issue with our IPv6 peering with the MICE route servers, Charter, and TDS and I'm looking for a larger audience to see if it's my issue or perhaps an issue at the exchange. I believe it to be the latter, but I'm not an IPv6 expert. Starting two days ago around 8am CDT, we started experiencing BGP timeouts on some of our IPv6 BGP sessions. I was able to work around the issue by removing our COPP policy and the BGP sessions were stable for 24 hours. Reapplied the policy, sessions started to drop again. Looked at the policy to see which category is being exceeded, it's not the routing section which allows BGP/BFD/etc, but the ICMP-v6 one: ipv6 access-list COPP-icmp-v6 remark ICMP type 1/3,2,3/0,3/1,4/0,4/1,4/2,130,143 permit icmp any any destination-unreachable permit icmp any any packet-too-big permit icmp any any time-exceeded permit icmp any any parameter-problem remark nd-na, nd-ns, ra, rs permit icmp any any nd-na permit icmp any any nd-ns permit icmp any any router-advertisement permit icmp any any router-solicitation remark MLD - query, report_v2 permit icmp any any mld-query permit icmp any any 143 which is being policed like this: class Icmp-v6 police 32000 60000 120000 conform-action transmit exceed-action drop I've worked around the issue by making a 4x increase in the policing, but the question I have is what happened at the exchange to provoke my COPP policy? Alternatively, is this normal or indicate who has the problem: r-pop-min-1#deb ipv6 icmp ICMP Packet debugging is on r-pop-min-1# Jul 17 14:36:08.143 CDT: ICMPv6: Received N-Solicit, Src=FE80::56E0:3200:50CE:4178, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.281 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.281 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.285 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.359 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.433 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.435 CDT: ICMPv6: Sent N-Solicit, Src=FE80::CA4C:75FF:FE23:805, Dst=2001:504:27::8252:0:1 Jul 17 14:36:08.459 CDT: ICMPv6: Received N-Advert, Src=2001:504:27::8252:0:1, Dst=FE80::CA4C:75FF:FE23:805 Jul 17 14:36:08.535 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.535 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.539 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.559 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::8252:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:08.586 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::B664:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:08.617 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.687 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.782 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:08.783 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:08.783 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 r-pop-min-1# Jul 17 14:36:08.842 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.990 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.028 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.070 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.148 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.203 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.322 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.322 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.327 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.399 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.439 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.481 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.533 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::B664:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:09.572 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.572 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.581 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.608 CDT: ICMPv6: Received N-Solicit, Src=FE80::2E21:72FF:FE71:37B1, Dst=FF02::1:FF00:1 Jul 17 14:36:09.613 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::8252:0:1, Dst=FF02::1:FF00:1 r-pop-min-1# Jul 17 14:36:09.659 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.831 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:09.831 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:09.831 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:09.884 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.069 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.172 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.240 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.320 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.364 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.441 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.521 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.573 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.573 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.588 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::B664:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:10.622 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.659 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::8252:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:10.684 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.817 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.830 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:10.830 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:10.830 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:10.853 CDT: ICMPv6: Received type 130, Src=FE80::21B:DFF:FEE7:15C0, Dst=FF02::1 r-pop-min-1# Jul 17 14:36:10.908 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.925 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 I'm thinking that the answer is that this is not normal, as it looks like I'm getting duplicate solicitations in the same second. -James ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

4 5

MICE UG 13 - Duluth July 24th Note 2PM start
by Mike Hemphill July 21, 2014

July 21, 2014

Good Afternoon All! MICE UG 13 has been scheduled, as follows: Date: Thursday, July 24th Time: 2:00 pm (1400 Hours) David Farmer has the facility reserved until 5PM Location: University of Minnesota, Duluth campus, Griggs Center, located in the *Kirby Student Center (KSC) * http://www.d.umn.edu/maps/KSC/ Please send your agenda items when you have a chance! Also please invite business & other entities that may have an interest in connecting to MICE. Our goal is to extend the reach of MICE connectivity to outstate institutions & companies. Thanks! Reid, Shaun & Mike *Mike Hemphill* *General Manager | **Cologix, Inc. <http://www.cologix.com/>* *511 11th Ave S, Suite 450 | Minneapolis, MN 55415P: 1+612.333.1922 | M: 1+612.812.5242mike.hemphill(a)cologix.com <mike.hemphill(a)cologix.com>* ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

6 5

Please welcome 702 Communications to MICE
by Jay Hanke July 10, 2014

July 10, 2014

Name: 702 Communications Port: CNS switch gi0/4 ASN: 15627 IPv4: 206.108.255.54/24 IPv6: 2001:504:27:0:0:3d0b::1/64 Peering Contact: dpoehls(a)702communications.com Route Servers and website please! Welcome aboard! -- Jay Hanke CEO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

2 1

Please Welcome Acentek to MICE
by Jay Hanke July 4, 2014

July 4, 2014

Acentek ASN: 40328 Port: Kato Remote Switch ge-0/0/15 IPv4: 206.108.255.109/24 IPv6: 2001:504:27:0:0:9D88::1/64 Peering contact: peering(a)acentek.net Estimated activation 8/1/14 Website and route servers please. Welcome aboard! -- Jay Hanke CEO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

3 2

a poll about operators (that's you) participating in the IETF
by Mike O'Connor June 14, 2014

June 14, 2014

hi all, thought that some of you might find this interesting. and some of you might want to blast through the poll. mikey http://www.circleid.com/posts/20140612_the_ietfs_other_diversity_challenge/ The IETF's *Other* Diversity Challenge Jun 12, 2014 10:32 AM PDT Comments: 0 Views: 1,013 Print Comment By Chris Grundemann The Internet Engineering Task Force (IETF) is the standards body for the Internet. It is the organization that publishes and maintains the standards describing the Internet Protocol (IP – versions 4 and 6), and all directly related and supporting protocols, such as TCP, UDP, DNS (and DNSSEC), BGP, DHCP, NDP, the list goes on, and on. In their own words: The mission of the IETF is to make the Internet work better by producing high quality, relevant technical documents that influence the way people design, use, and manage the Internet. But how do they do that? How does the IETF produce documents, and ensure that they are high quality, relevant, and influential? Without going into too much boring detail here, the IETF uses a system of grassroots collaboration that is really quite revolutionary in many ways. The IETF is split into broad focus "Areas" and then again into specific "Working Groups" that each target a single problem or technical topic. While there is leadership at each level, the real power of the IETF is that all the real innovation and decision making happens out on the edges, from the bottom-up rather than the top-down. Combine this grassroots collaboration within each working group with the bottom-up decision making power vested in them and then add in the openness for anyone to join any working group any time, and you start to see the magic of the IETF. All work is contributed by individuals, all decisions are based on rough consensus and running code, and the whole thing "just works." But does it work as well as it could? Nothing is perfect, of course, so shouldn't we always strive for improvement? One area that can almost always be improved in any global organization is diversity. The great benefit of an open organization, like the IETF, is that anyone can have his or her voice heard. The great tragedy is that only those who speak up can ever be heard. This makes who is participating very important indeed. We want as many voices from as many backgrounds as possible to ensure the best achievable outcome. Without having all the right people involved, we run the risk of missing something key, for lack of their perspective. The IETF is already aware of the importance of diversity and steps are being taken to help ensure representation in the IETF from all areas of the world, and more equal representation from both genders. The Internet Society Fellows program helps bring folks from around the globe who wouldn't otherwise be able to participate to IETF meetings and there is a diversity design team with an open mailing list for community (that's you) feedback to help them in "identifying diversity related issues that the IETF faces and making practical recommendations that can help in this regard." I applaud these efforts! Each of us should contribute to them, and to the overall diversity dialogue, in every way we can. But I see another diversity issue at play in the IETF as well, and I've come to learn that I'm not alone. This "other diversity challenge" may be a bit more subtle and harder for those not familiar with the Internet industry to see. The physical differences between Operators, Vendors, and Academics are markedly less than those between men and women. The differences in perspective, however, may actually be far greater in both scope and scale. The differences in the way that someone actively running a network views a problem, and the way that same problem is seen by someone writing code for routers are significant. The same goes for either of those two and someone conducting network research. We need all three of these broad views, and all the myriad of views that each contain, informing our innovation and our decision making at the IETF. Currently, it seems, that is not entirely the case. Many believe that the level of operational input into the IETF is too low. That's not to say there are no operators at the IETF, nor to infer that the operators who do participate already are somehow inadequate. Quite the opposite. Just as the first women, or Latin Americans, or Africans, or Asians to participate in the IETF paved the way for more diversity, those operators who participate today, who have participated in the past — and especially those who have participated all along — have kept the door open for additional operator input. One shining example of this is the IEPG, or Internet Engineering and Planning Group, who meet the Sunday before every IETF meeting to discuss operational issues. How do we expand on that? How do we ensure that network operators, those folks responsible for keeping the packets flowing across their (service provider, enterprise, data-center, campus, cloud, etc.) networks, are always included in those who are working to influence the way we design, use, and manage the Internet? To answer that, my team at the Internet Society decided first to research the issue. We want to know if there are, in fact, barriers to operator involvement in the IETF, and if so, what they are. This is where *you* come in. We have an informal survey posted specifically to gather information from network operators about the IETF. We particularly want to hear from folks who are network operators but do not currently participate in the IETF; we want to know why! So if you operate a network, please take our survey, and whether you do or not, please share it as well. We want to hear from people you know, in your part of the world, as well as everywhere else! The survey will close after the last day of June. On the first of July we'll begin synthesizing everything we've heard. Then we'll present it back to the global network engineering community, to network operators the world round. We'll also present it to the IETF, to share our findings and amplify the voice of the operators. Once we know we've heard everything, and recorded it correctly, we'll start working on solutions to any identified problems. I believe we'll be able to classify the solutions we find based on who is needed to implement them. There will likely be a set of things that operators themselves, or more likely operator groups, can do to help. There will probably be another set of improvements or changes that the IETF itself can make to improve operator engagement and operational input. Finally, I think we may also find some things that the Internet Society can do to help facilitate these interactions. But before we can even think about solutions, we must first define the problems. Please help us in this effort, take and share this survey before 31 June 2014 (shortlink: http://bit.ly/opsietfsurvey) Thank you! By Chris Grundemann, Internet Technologist, Author, and Speaker. All opinions are his and his alone. More blog posts from Chris Grundemann can also be read here. PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

1 0

Please welcome Code42 to MICE
by Jay Hanke June 10, 2014

June 10, 2014

Name: Code42 ASN: 62715 Main switch port xe-0/0/19 IPv4: 206.108.255.32/24 IPv6: 2001:504:27:0:0:f4fb::1/64 Contact: peering(a)code42.com Route servers and website please. Welcome aboard! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

4 3

Akamai (20940) < > MICE IXP Brief Maintenance
by Hannigan, Martin June 9, 2014

June 9, 2014

Folks, You may have seen our traffic drop off. We are conducting a brief maintenance. Traffic should return to normal levels shortly. Best, -M< ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

1 1

Please welcome Monticello Fibernet to MICE
by Jay Hanke May 21, 2014

May 21, 2014

Monticello Fibernet will be connecting to port ge-0/0/8 of the Mankato Networks remote switch. I have assigned 206.108.255.108 for their IPv4 connection. Their ASN is pending with ARIN. Please update the website. I will send out another announcement with their ASN and IPv6 subnet as soon as the ASN has been assigned. Thanks! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

Wrapping up my time at ICANN
by Mike O'Connor May 10, 2014

May 10, 2014

hi all, just a quick note to announce my retirement from ICANN. i know i haven’t deluged you with lots of posts and rumpus, but i did my best to represent the views of MICE while i was there. my focus was almost entirely on nudging ICANN to do a better job at the security and stability of the DNS. thanks for letting me do that. mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Port Security
by Jeremy Lumby May 6, 2014

May 6, 2014

At the last meeting there was a group that was going to email out the proposed process to secure the ports on the MICE switches. I was just wondering how that was coming along. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Summer MICE Joint meeting
by Jay Hanke April 12, 2014

April 12, 2014

I'd like to throw out MKE or Madison as a venue for the summer meeting. I also reached out to KCIX and they are interested in coming up. I sent an email to MBIX but haven't heard back yet. There is a fair amount of interest from the OpenIX folks. There is a fair amount of OpenIX activity across the border in IL. Wisconsin folks, can we get a sponsor (location/food)? Needs to be close to an airport -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

5 7

Website Update
by Richard Laager April 6, 2014

April 6, 2014

I've cut in the new website design (thanks MDU Ethernet!). If you see any problems, please let me know. -- Richard ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

6 10

MICE Cacti Server - To Be Rebooted
by Justin Krejci March 27, 2014

March 27, 2014

As the server was not originally setup to run Cacti it does not have a desirable amount of CPU and RAM. Since it is a VM the process to upgrade the hardware is barely more time than a shutdown and boot up will take. I am going to do this shortly so the server/site will be offline for a few minutes and there'll be a small gap in the data possibly. I will try and time it to be in between polling intervals so it may not even miss any data. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 2

UG 12 Minutes
by Shaun Carlson March 26, 2014

March 26, 2014

Please see attached. Talk to Reid if you have any questions. s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

4 3

micemn-01.micemn.net route reflector at 206.108.255.1
by Doug McIntyre March 24, 2014

March 24, 2014

We've noticed this being unresponsive several times this evening. I'm into the machine, but it is behaving badly, and from past experience, (and not direct evidence since it is remote and I can't get the relavent logs), it feels like a hard drive failing on this system. Ie. it may run some of its process out of memory for some functions, but other functions are probably locking up and not behaving correctly. Even RAIDed as it is. Probably the best course of action is to bring out a fresh drive to it and swap whatever drive is failing and let the mirror rebuild. I think we've got some of the 80GB WD800AAJS that is part of the mirror on the other route reflector around somewhere... -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

6 15

MICE User Group meeting next Wednesday
by Mike Hemphill March 21, 2014

March 21, 2014

All, Just a quick meeting reminder for our upcoming UG meeting on Wednesday, March 26th at 4:00 PM in the 511 Building cafeteria. Please send Shaun, Reid and me any agenda items you may have or any topics you want to be sure are covered. We currently do not have a sponsor for food & beverages, if your company is willing to step up, please let us know. Thanks! Mike Mike Hemphill General Manager | *Cologix, Inc.* <http://www.cologix.com/> 511 11th Ave S, Suite 450 | Minneapolis, MN 55415 P: 1+612.333.1922 | M: 1+612.812.5242 mike.hemphill(a)cologix.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

10 13

Akamai (20940) < > MICE IXP Upgrade to 2x10G
by Hannigan, Martin March 20, 2014

March 20, 2014

Everyone, All paperwork has been completed and Akamai will be upgrading to 20G. FYI. Best Regards, Martin Hannigan Director, Network and Data Center Architecture Akamai Technologies, Inc. ASN 20940 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Please Welcome Radio Link Internet to MICE
by Jay Hanke March 19, 2014

March 19, 2014

main switch: xe-0/0/17 Radio Link Internet AS: 53301 206.108.255.31/24 2001:504:27:0:0:d035::1/64 daniel.petsinger(a)radiolinkinternet.com Prefix Limit 25 They will be providing an optic for their 10G fiber connection. Route-server and defaulting graphing please. Thanks! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

NTIA announcement about ICANN transition to independent entity
by Mike O'Connor March 15, 2014

March 15, 2014

hi all, i’m presuming most of you have seen the NTIA announcement by now. since i hang “MICE" on my nametag when i participate in ICANN meetings, i thought i’d push along some observations, and some links to detailed info that may not find its way into the press coverage. the announcement: http://www.ntia.doc.gov/press-release/2014/ntia-announces-intent-transition… WASHINGTON – To support and enhance the multistakeholder model of Internet policymaking and governance, the U.S. Commerce Department’s National Telecommunications and Information Administration (NTIA) today announces its intent to transition key Internet domain name functions to the global multistakeholder community. As the first step, NTIA is asking the Internet Corporation for Assigned Names and Numbers (ICANN) to convene global stakeholders to develop a proposal to transition the current role played by NTIA in the coordination of the Internet’s domain name system (DNS). the FAQ on ICANN’s site; http://www.icann.org/en/about/agreements/iana/functions-transfer-faqs-14mar… want to know a LOT about these issues (like PhD level)? Here’s Samantha Dickinson’s summary of a boatload of submissions from all over the place that’s going into the upcoming Net Mundial meeting in Brazil. read all these (like i am right now) and you’ll know where the proposals lie. http://linguasynaptica.com/netmundial-submissions-on-iana/ my view is mostly “keep calm and peer on.” i’m hoping the transition could be the same level of non-event that taking down the NSF backbone network was. on the other hand, we don’t know how this is actually going to turn out until it’s done. the fearmongers in Washington aren’t being helpful. my view “from the bottom of the bottom-up process” is that i’ll be an interested observer and i’ll probably continue to put most of my energy into the day-to-day policy stuff. that’s the stuff that makes ICANN legitimate. i was on a conference call this morning where the CEO (Fadi Chehadi) and the Chair of the Board (Steve Crocker - author of RFC 0001) talked to community members about what’s going on. the points i raised were mostly about bandwidth (the community is already really overloaded) and process (a good project plan would be nice). happy to try to answer questions, although i’m still coming up to speed myself — this came as a surprise to almost everybody. i’m headed to the ICANN meeting in Singapore (leaving this Wednesday, back the following Friday). the outlines will be clearer after that. mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

DDoS Attacks
by Richard Laager March 13, 2014

March 13, 2014

Last night, we got hit by a ~3 Gbps DDoS attack. It's been a while since this has happened to us, so I'd like to make sure I'm still up on the state of the art. Is there anything more to be done than the following? 1. Identify the victim. 2. Null route the victim. 3. Propagate the null route to your upstreams (via BGP, if supported, otherwise a phone call to their NOC). 4. Move the victim to a new IP. To avoid participating in at least some classes of DDoS attacks, we: * long ago implemented uRPF (and/or similar ACLs) to block spoofed outbound packets, as recommended by BCP 38 (RFC 2827). * ensured our NTP servers (and any NTP servers of our customers) are not responding to monlist queries. The openntpproject.org website is useful here. They list vulnerable NTP servers by IP range, or you can get all NTP servers by AS (replace YOUR_AS with your AS, and optionally, add &csv=1) and then query with ntpdc -n -c monlist IP: http://openntpproject.org/searchby-asn.cgi?search_asn=YOUR_AS * just this week started addressing customers with open DNS resolvers, which can also be used in amplification attacks: http://openresolverproject.org/searchby-asn.cgi?search_asn=YOUR_AS Is there anything else we should be doing? -- Richard ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

4 3

Re: bgp flapping to 206.108.255.1
by Frank DiGravina March 13, 2014

March 13, 2014

Hello, I am shutting our peering to 206.108.255.1 until I see notice that that your route-reflector issue has been addressed. Thanks, Frank -- Frank DiGravina University of Minnesota Networking & Telecommunications Network Operations Phone: 612-626-9074 Cell: 612-386-0449 E-Mail: digravin(a)umn.edu Helpline: 612-301-HELP ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

XO issues Sunday morning?
by Frank Bulk March 10, 2014

March 10, 2014

This isn't a MICE-related question, but since so many MICE members are in the Minnesota area I thought I would ask. Sunday morning from 1:11 am to about 4:20 am we saw an unusually high number of websites time out over IPv6. We monitor 50 IPv6-enabled web sites over IPv6, performing both an ICMP check (if possible) and then HTTP over IPv6. There were at least 17 sites during that time frame that timed out on our monitoring systems' HTTP GET request. One pattern emerged -- 14 of them traceroute through an XO link that goes through Minneapolis. Here's a sample: traceroute to ipv6.test.Level3.com (2001:1900:2018:3000::105) from 2607:fe28:0:1000::5, port 80, from port 36274, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.395 ms 0.325 ms 0.319 ms 2 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 0.188 ms 0.135 ms 0.185 ms 3 v6-premier.sxcy-mlx.fbnt.netins.net (2001:5f8:7f0a:2::1) 1.612 ms 1.545 ms 1.613 ms 4 v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1) 6.667 ms 6.566 ms 8.002 ms 5 v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1) 6.624 ms 7.995 ms 6.602 ms 6 2610:18:18b:c000::11 (2610:18:18b:c000::11) 12.108 ms 12.075 ms 12.137 ms 7 mcr1.minneapolis-mn.us.xo.net (2610:18::30b8) 21.431 ms 21.452 ms 21.421 ms 8 vb1710.rar3.chicago-il.us.xo.net (::ffff:216.156.0.169) 30.701 ms 23.639 ms 23.771 ms .... I then looked at the daily traceroutes we have on file for all 50 sites we monitor and it looks like 15 of them go through XO. So over 93% (14 out of 15) of the sites that go through XO timed out during the 1:11 am to 4:20 am time period. Did anyone with XO connectivity see issues Sunday morning? Frank ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

2 x 10GE Contact?
by Hannigan, Martin March 7, 2014

March 7, 2014

Who can I talk to about adding a second 10G? Best, , -M< ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Public Stats Aggregate View
by Brady Kittel Feb. 27, 2014

Feb. 27, 2014

Any update on when we'll be adding the aggregate ingress+egress stats to the main page of the MICE site as was discussed in the minutes for the last UG? I only ask as I'd like to update MICE on the Wikipedia article listing IX's by total throughput but I need the public graph to cite for the update. Currently they're listing MICE at 10Gbit for throughput. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

4 7

Re: Google Global Cache Interest?
by Dan Olsen Feb. 26, 2014

Feb. 26, 2014

Reid. Do you need member support to help with Netflix etc Sent from my Verizon Wireless 4G LTE DROID Reid Fishler <rfishler(a)HE.NET> wrote: >I am already on Netflix also...just not as good results yet. I am working on it. > > >Reid > > > >On Fri, Feb 21, 2014 at 5:34 PM, Nathan Beard <nbeard(a)stellarllc.net> wrote: > >I for one would have interest in utilizing a Google cache server if MICE were to implement this. > >Also, are there any updates regarding a potential MICE to Netflix peering solution? I know that 511 isn't listed as a public peering location on the Netflix Open Connect website, but I seem to recall that discussions have been underway for some time in an attempt to make this happen. I would be very interested if somebody had information to share on this, since it is something that be of great benefit to Stellar. > >Thanks! > > > > > >On 02/21/2014 04:19 PM, Russell Berg wrote: > >Some MICE peers already have Google (and other) caches, so you may have to poll to see who would be participating in a Google cache at MICE to get more accurate bandwidth measurements. Russ Airstream Communications -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Brady Kittel Sent: Friday, February 21, 2014 9:11 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Google Global Cache Interest? Not sure if maybe someone has already looked into this. On a wild hair I filled out the inquiry form for looking at a Google Global Cache cluster for our site and also mentioned there is an IX they might be able to connect to as an alternative option. We're a bit below their peak cachable content requirements however I have no doubt MICE would far exceed them. Would there be any interest in placing one on MICE for members to share? ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: 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 > > > >To unsubscribe from the MICE-DISCUSS list, click the following link: >http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > > >-- >Reid Fishler >Director >Hurricane Electric >+1-510-580-4178 > > >To unsubscribe from the MICE-DISCUSS list, click the following link: >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

2 1

Google Global Cache Interest?
by Brady Kittel Feb. 24, 2014

Feb. 24, 2014

Not sure if maybe someone has already looked into this. On a wild hair I filled out the inquiry form for looking at a Google Global Cache cluster for our site and also mentioned there is an IX they might be able to connect to as an alternative option. We're a bit below their peak cachable content requirements however I have no doubt MICE would far exceed them. Would there be any interest in placing one on MICE for members to share? ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

8 10

Re: Netflix
by Jeremy Lumby Feb. 21, 2014

Feb. 21, 2014

I have had conversations with Netflix about peering in Minneapolis, and they have said that the project has existed for years, however it keeps getting bumped back for other projects (European expansion is one that they mentioned). I do not have a great direct contact to do some arm twisting with. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Nathan Beard Sent: Friday, February 21, 2014 4:35 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Google Global Cache Interest? I for one would have interest in utilizing a Google cache server if MICE were to implement this. Also, are there any updates regarding a potential MICE to Netflix peering solution? I know that 511 isn't listed as a public peering location on the Netflix Open Connect website, but I seem to recall that discussions have been underway for some time in an attempt to make this happen. I would be very interested if somebody had information to share on this, since it is something that be of great benefit to Stellar. Thanks! On 02/21/2014 04:19 PM, Russell Berg wrote: Some MICE peers already have Google (and other) caches, so you may have to poll to see who would be participating in a Google cache at MICE to get more accurate bandwidth measurements.RussAirstream Communications-----Original Message-----From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Brady KittelSent: Friday, February 21, 2014 9:11 AMTo: MICE-DISCUSS(a)LISTS.IPHOUSE.NETSubject: [MICE-DISCUSS] Google Global Cache Interest?Not sure if maybe someone has already looked into this. On a wild hair I filled out the inquiry form for looking at a Google Global Cache cluster for our site and also mentioned there is an IX they might be able to connect to as an alternative option. We're a bit below their peak cachable content requirements however I have no doubt MICE would far exceed them. Would there be any interest in placing one on MICE for members to share?########################################################################To unsubscribe from the MICE-DISCUSS list, click the following link:http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1###########… unsubscribe from the MICE-DISCUSS list, click the following link: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 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

Re: Multicast on MICE?
by Danny Meister Feb. 21, 2014

Feb. 21, 2014

Not multicast, but we saw really high utilization on our MICE link for the past few hours, probably due to USA/Canada hockey. Its tapering off now to normal levels. -Danny Danny Meister - Network Engineer, Level II Atomic Data 615 North 3rd Street Minneapolis, MN 55401 612.466.2000 Main Line 612.466.2071 Direct Dial Twitter<http://twitter.com/AtomicData> | Facebook<http://www.facebook.com/AtomicDataCenters> | LinkedIn<http://www.linkedin.com/companies/atomic-data-centers> Simple. Safe. Smart. www.atomicdata.com<http://www.atomicdata.com/> From: Anthony Anderberg <anthonyanderberg(a)NU-TELECOM.NET<mailto:anthonyanderberg@NU-TELECOM.NET>> Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> Date: Friday, February 21, 2014 at 12:46 PM To: "MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>" <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> Subject: [MICE-DISCUSS] Multicast on MICE? Is anyone doing substantial IP multicast across MICE today (IPTV, ect)? Anthony Anderberg Sr. Systems Analyst [NUtel_email_logo_1] 320-234-5239 anthonyanderberg(a)nu-telecom.net<mailto:anthonyanderberg@nu-telecom.net> www.nutelecom.net ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: 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

1 0

Multicast on MICE?
by Anthony Anderberg Feb. 21, 2014

Feb. 21, 2014

Is anyone doing substantial IP multicast across MICE today (IPTV, ect)? Anthony Anderberg Sr. Systems Analyst [NUtel_email_logo_1] 320-234-5239 anthonyanderberg(a)nu-telecom.net<mailto:anthonyanderberg@nu-telecom.net> www.nutelecom.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

AS33125 (Spiralight) removal from MICE
by Andrew Hoyos Feb. 20, 2014

Feb. 20, 2014

Hi folks, As you may know, Wisconsin Independent Network (WIN) recently purchased the most of the assets of Spiralight Network, and they have been working to fold those into their network. As such, the AS33125 MICE port was turned off this morning, and will stay down. Just a FYI for folks, to clean up sessions/route servers/member info page, etc. AS33125 will continue to operate as Bug Tussel Wireless (which was a sister company to Spiralight), however, just with a Wisconsin footprint. Thanks! Andrew -- Andrew Hoyos Hoyos Consulting LLC ofc: +1 608 616 9950 andrew(a)hoyosconsulting.com http://www.hoyosconsulting.com/ ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Re: Mice Issues
by Jeremy Lumby Feb. 20, 2014

Feb. 20, 2014

I think we should revisit the topic of how to better protect MICE from these Layer 2 issues that we have had a few of in the history of MICE. I feel that stability is extremely important, especially when it comes to attracting new members, as well as getting existing members to increase their capacity. I know that many of the Layer 2 security measures that are possible for the exchange increase the amount of administrative time that needs to be put into the exchange, however I feel it may be very well worth the extra work when adding/maintaining members' connections I was looking through my log files, and during the outage, I saw a bunch of entries stating: %IPV6-3-CONFLICT: Router FE80::21D:71FF:FE98:74C0 on GigabitEthernet0/2 has conflicting ND settings I am not very familiar with this error, and not sure if it was just as a result of the degraded conditions on MICE, or if it had something to do with the cause. Jeremy ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

MICE Traffic
by Jay Hanke Feb. 20, 2014

Feb. 20, 2014

It looks like we ran over 29 Gb/s of legit traffic (in+out) earlier this afternoon! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Re: Mice Issues
by Jeremy Lumby Feb. 20, 2014

Feb. 20, 2014

Charter Update: I am providing this update to let others know what I went through after the outage to get re-connected to Charter in the event that others are seeing similar issues, hopefully it can cut a lot of troubleshooting time. -When the outage happened yesterday I shut down my MICE port. -All traffic shifted to my other upstreams as expected, other than Charter -I could not pass 2 way traffic with anyone on Charter's network. -Some traceroutes from Charter's side showed that traffic heading to me was hitting their peering router that was connected to MICE, even though my BGP session with them had been down for hours -Charter's peering router showed that my BGP session was still established through MICE from prior to the outage starting. -Charter attempted to clear the BGP connection to me as well as do a shutdown on my neighbor statement, however whenever they looked at it, it still showed established with the timer reflecting it being up prior to the MICE outage. -I turned my MICE port back up, and return traffic from Charter started making it to me, despite BGP being down from my point of view. -It took Charter removing all of their neighbor statements to me, and re-entering them before BGP properly re-established in both directions. -The entire time our IPv6 session worked as expected -We are both running Cisco hardware, I believe they have a 9K and I have a 7206VXR-G2 I hope this helps others out with troubleshooting in the future Jeremy -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of David Farmer Sent: Wednesday, February 19, 2014 5:58 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Mice Issues On 2/19/14, 17:45 , Jeremy Lumby wrote: > Is anyone else having issues with connectivity to Charter? I have > re-established connectivity to every one else through my other > upstreams, other than Charter. I am keeping my MICE port down > overnight for good measure. Our peering with Charter has reestablished via MICE, everything looks good here. -- ================================================ David Farmer Email: farmer(a)umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 1-612-626-0815 Minneapolis, MN 55414-3029 Cell: 1-612-812-9952 ================================================ ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: 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

1 0

Re: Mice Issues
by Jeremy Lumby Feb. 19, 2014

Feb. 19, 2014

Is anyone else having issues with connectivity to Charter? I have re-established connectivity to every one else through my other upstreams, other than Charter. I am keeping my MICE port down overnight for good measure. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Dan Boehlke Sent: Wednesday, February 19, 2014 5:41 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Mice Issues The Vaultas switch has been configured to participate in spanning-tree, so it won't blindly go along with loops any more. Sorry. The Vaultas switch didn't make the loop, it just made it worse. Any word on the origination of the loop? -- Dan Boehlke dboehlke(a)mac.com On Feb 19, 2014, at 4:47 PM, Jay Hanke <jayhanke(a)MANKATONETWORKS.NET> wrote: Got ssh, that mac doug sent out belongs to Vaultas. On Wed, Feb 19, 2014 at 2:27 PM, Jay Hanke <jayhanke(a)mankatonetworks.net> wrote: There are two Extreme networks on the Mankato Remote switch, Vaultas and Revnet. I don't have ssh right now, can someone check? On Wed, Feb 19, 2014 at 2:21 PM, Doug McIntyre <merlyn(a)iphouse.net> wrote: On Wed, Feb 19, 2014 at 04:03:15PM -0600, Richard Laager wrote: Can someone look at the route server logs and see who the new IPv4 peer was that showed up just before this problem started? Nobody turned up recently. A better measure is who turned up on the switch rather than the route-server. This was a l2 flood, not anything in routing. No ports were up/down on the switch until the flood triggered my port and Implex's port offline (probably the same class of cisco switch protecting themselves from the l2 flood). Feb 19 15:11:45 MICE-SW1 mib2d[1107]: SNMP_TRAP_LINK_DOWN: ifIndex 604, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-1/0/3 Feb 19 15:11:48 MICE-SW1 mib2d[1107]: SNMP_TRAP_LINK_DOWN: ifIndex 606, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-1/0/5 So, it probably was from one of the existing remote switches. The MAC address I posted about before is an Extreme? switch. Also, the l2 flood seems abated. I've been pinging clear to the route servers for 5 minutes now. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: 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 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Mice Issues
by Jeremy Lumby Feb. 19, 2014

Feb. 19, 2014

I have been experiencing packet loss, as well as seen many of my BGP sessions go down across MICE. Has anyone else seen issues? ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

15 28

Please welcome Emergent Networks to MICE!
by Jay Hanke Feb. 6, 2014

Feb. 6, 2014

Port: xe-0/0/35 Emergent Networks ASN: 29762 IPv4: 206.108.255.30/24 IPv6: 2001:504:27:0:0:7442::1/64 peering(a)emergentnetworks.com Prefix Limit: 15 Please update route servers and website! Welcome aboard! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Traffic Drop
by Dean Bahls Feb. 4, 2014

Feb. 4, 2014

Wondering if anyone knows the specifics behind the dramatic drop in MICE traffic that started about a week ago. Thanks! Dean Dean Bahls Network Services Manager Cooperative Network Services, LLC (218) 346-3635 (office) dean.bahls(a)cooperative-networks.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

8 13

Mice Meeting Tomorrow @ 4 pm
by Shaun Carlson Jan. 31, 2014

Jan. 31, 2014

Good morning all! Just a friendly reminder of our 4 pm meeting tomorrow at the 511 building. I'm assembling the agenda now, if you have anything to include for discussion, please send it my way! s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

5 8

UG 11 Minutes
by Shaun Carlson Jan. 31, 2014

Jan. 31, 2014

Please see attached. s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

3 4

UG 11 Agenda
by Shaun Carlson Jan. 30, 2014

Jan. 30, 2014

Please see attached... s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 1

Re: Mice Meeting Tomorrow @ 4 pm
by Mike Johnston Jan. 30, 2014

Jan. 30, 2014

What is this weather you speak of? We are to St. Cloud already and the weather is wonderful. Mike Johnston Wikstrom Telephone Company Eric Crist <ecrist(a)CLAIMLYNX.COM> wrote: >I'd be interested in a WebEx session for tonight's meeting. > >--- >Eric F Crist >System Administrator >ClaimLynx, Inc >(952) 593-5969 x2301 > > > >On Jan 30, 2014, at 10:59:16, Shaun Carlson <shaun.carlson(a)ARVIG.COM> wrote: > >> Yes, we're still planning to have the meeting. >> >> I was thinking about offering a webex for those that can't travel to the cities. If you're interested in that option, please let me know. >> >> s >> >> On Thursday, January 30, 2014, Eric Crist <ecrist(a)claimlynx.com> wrote: >> With the weather being what it is, is the plan to still hold the meeting? >> >> --- >> Eric F Crist >> System Administrator >> ClaimLynx, Inc >> (952) 593-5969 x2301 >> >> >> >> On Jan 29, 2014, at 10:10:17, Shaun Carlson <shaun.carlson(a)ARVIG.COM> wrote: >> >> > Good morning all! >> > >> > Just a friendly reminder of our 4 pm meeting tomorrow at the 511 building. >> > >> > I'm assembling the agenda now, if you have anything to include for discussion, please send it my way! >> > >> > s >> > >> > Shaun Carlson >> > Network Engineering Manager | Arvig >> > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com >> > >> > To unsubscribe from the MICE-DISCUSS list, click the following link: >> > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >> > >> >> >> -- >> This e-mail and any files transmitted with it are confidential and are >> intended solely for the use of the individual or entity to whom they are >> addressed. If you are not the intended recipient or the individual >> responsible for delivering the e-mail to the intended recipient, please be >> advised that you have received this e-mail in error and that any use, >> dissemination, forwarding, printing, or copying of this e-mail is strictly >> prohibited. >> >> If you have received this communication in error, please return it to the >> sender immediately and delete the original message and any copy of it from >> your computer system. If you have any questions concerning this message, >> please contact the sender or call ClaimLynx at (952) 593-5969. >> >> ######################################################################## >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >> >> >> -- >> >> Shaun Carlson >> Network Engineering Manager | Arvig >> ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com >> >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >> > > >-- >This e-mail and any files transmitted with it are confidential and are >intended solely for the use of the individual or entity to whom they are >addressed. If you are not the intended recipient or the individual >responsible for delivering the e-mail to the intended recipient, please be >advised that you have received this e-mail in error and that any use, >dissemination, forwarding, printing, or copying of this e-mail is strictly >prohibited. > >If you have received this communication in error, please return it to the >sender immediately and delete the original message and any copy of it from >your computer system. If you have any questions concerning this message, >please contact the sender or call ClaimLynx at (952) 593-5969. > >######################################################################## > >To unsubscribe from the MICE-DISCUSS list, click the following link: >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

1 0

"Toward Efficiencies in Canadian Internet Traffic Exchange" - a good read for us too, i think
by Mike O'Connor Jan. 29, 2014

Jan. 29, 2014

hi all, i was thinking this might be interesting for y’all, even though it’s got a Canadian slant. lots of their arguments apply to us as well, no? i’m reluctant to hit this list with a 2.5 mB attachment, so here’s a link http://www.cira.ca/assets/Uploads/Toward-Efficiencies-in-Canadian-Internet-… here are a few teaser bullet points from the first page Key benefits: By reducing reliance on costly international data transit, additional ISPs will reduce networks’ ongoing operational costs. These cost savings will flow to Canadian Internet users, and unnecessary export of capital will be reduced. By providing high-speed domestic links, additional ISPs will increase the amount of bandwidth available to Canadian users, mitigating networks’ bandwidth shortages and removing networks’ incentives to impose bandwidth throttling and usage caps. By favoring shorter and more direct routes, additional ISPs will reduce network latency, improving the performance of new services like video and could-based applications. By allowing Canadian data to remain in Canada as much as possible and as often as possible, additional ISPs will reduce the risk of Canadian data becoming subject to foreign laws and practices. By increasing the richness and density of connections between Canadian networks, additional ISPs will increase the reliability of internet access in Canada and its resilience to disaster and attack. among other things, there’s an interesting discussion of Governance Structures about midway through this piece. there’s a Challenges and Responses section right after that. as a retired “suit,” i found it a good read. ;-) mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

Welcome HCMC to MICE!
by Jay Hanke Jan. 29, 2014

Jan. 29, 2014

HCMC Main Switch Port xe-0/0/36 ASN 40413 IPv4: 206.108.255.29 IPv6: 2001:504:27:0:0:9ddd::1 Contact: Daniel.Huwe(a)hcmed.org Max prefix: 15 Please update route server configurations and update the website. Thanks! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

3 2

Re: Traffic Drop
by Jeremy Lumby Jan. 22, 2014

Jan. 22, 2014

I noticed the same thing last Friday From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Dean Bahls Sent: Wednesday, January 22, 2014 9:30 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Traffic Drop Wondering if anyone knows the specifics behind the dramatic drop in MICE traffic that started about a week ago. Thanks! Dean Dean Bahls Network Services Manager Cooperative Network Services, LLC (218) 346-3635 (office) dean.bahls(a)cooperative-networks.com To unsubscribe from the MICE-DISCUSS list, click the following link: 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

3 2

Meeting Reminder / Agenda Request
by Shaun Carlson Jan. 20, 2014

Jan. 20, 2014

All, Just a quick meeting reminder for our upcoming UG meeting on Thursday, January 30th at 4:00 PM in the 511 cafeteria. Please send me any agenda items you may have or any topics you want to be sure are covered. Thanks! s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

Please welcome Supranet to MICE!
by Jay Hanke Jan. 13, 2014

Jan. 13, 2014

Supranet is connecting both of their ASNs to MICE via one port. AS: 4150 IPv4: 206.108.255.27 IPv6: 2001:504:27:0:0:1036::1/64 Port: ge-1/0/7 Main Switch (shared) Peering Contact: peering(a)supranet.net Route Servers: yes Max IPv4 Prefix: 250 AS: 5683 IPv4: 206.108.255.28 IPv6: 2001:504:27:0:0:1633::1/64 Port: ge-1/0/7 Main Switch (shared) Peering Contact: peering(a)supranet.net Route Servers: yes Max IPv4 Prefix: 250 Please email me back when the route server configuration is complete. Thanks! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

4 5

Cologix Maintenance..
by Doug McIntyre Jan. 9, 2014

Jan. 9, 2014

FYI: Since I remember some MICE members didn't receive Cologix's maintenace notices. Cologix has UPS/power maintenance right now (1/9/14), and MICE route reflector 1 (206.108.255.1) is down due to it. The route reflector #2 is up and still doing BGP. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

Re: Enventis Maintenance
by Jake Lubitz Jan. 3, 2014

Jan. 3, 2014

Update: We ran into a snag the other night (12/18) with this maintenance and had to move this event until after the holidays. As of 11:30AM today (1/3) we have our 10Gbps connection up, as well as BGP, to the MICE Juniper router. I apologize for the lack of updates on this. At any rate, the 10Gbps connection to MICE is up and happy at the moment. Please let us know if we missed anything. Thanks in advance. Jake ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

Cogent Transport
by Jay Hanke Dec. 25, 2013

Dec. 25, 2013

Does anyone on MICE have a Cogent L2 Transport Circuit? Could you contact me off-list? -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1