- mice-discuss - lists.micemn.net

AS33125 (Spiralight) removal from MICE

by Andrew Hoyos

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

Feb. 20, 2014

Re: Mice Issues

by Andrew Hoyos

I'd agree. I've posted this a few times before, but AMS-IX has an *excellent* guide on how to properly configure your ports facing the IX (both in routed port or layer2 port scenario). https://www.ams-ix.net/config-guide/ Spanning tree interaction between the IX and members is just a recipe for disaster. I think if everyone takes a few minutes to review that and properly configure ports, most of these concerns would be alleviated. Thanks! Andrew -- Andrew Hoyos Hoyos Consulting LLC ofc: +1 608 616 9950 andrew(a)hoyosconsulting.com http://www.hoyosconsulting.com/ On Feb 20, 2014, at 1:59 PM, Jeremy Lumby wrote: > 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 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Feb. 20, 2014

Re: Mice Issues

by Jeremy Lumby

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

Feb. 20, 2014

Re: MICE Traffic

by Mike Horwath

On Feb 20, 2014, at 3:38 PM, Jay Hanke <jayhanke(a)MANKATONETWORKS.NET> wrote: > It looks like we ran over 29 Gb/s of legit traffic (in+out) earlier > this afternoon! That’s awesome! -- Mike Horwath, reachable via drechsau(a)Geeks.ORG ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Feb. 20, 2014

MICE Traffic

by Jay Hanke

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

Feb. 20, 2014

Re: Mice Issues

by Jeremy Lumby

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

Feb. 20, 2014

Re: Mice Issues

by David Farmer

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

Feb. 19, 2014

Re: Mice Issues

by Dan Boehlke

So next question, which flavor of spanning tree is best. I configured PVST on a reflex, but remembered that the MICE switch is a Juniper, not a Cisco. Simple dot1d? -- Dan B. On Feb 19, 2014, at 5:50 PM, David Farmer <farmer(a)UMN.EDU> wrote: > On 2/19/14, 17:43 , Richard Laager wrote: >> On Wed, 2014-02-19 at 17:40 -0600, Dan Boehlke wrote: >>> The Vaultas switch has been configured to participate in spanning-tree >> >> Is that really what we want? > > There are philosophical arguments both ways on this one. Given our cooperative management there is an argument to having spanning tree there to catch us if/when we screw up. > > In a very tightly managed situation where there can be no loops then there is an argument to turn-off spanning tree, but god help you if there ever is a loop. > > > -- > ================================================ > 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

Feb. 19, 2014

Re: Mice Issues

by David Farmer

On 2/19/14, 17:43 , Richard Laager wrote: > On Wed, 2014-02-19 at 17:40 -0600, Dan Boehlke wrote: >> The Vaultas switch has been configured to participate in spanning-tree > > Is that really what we want? There are philosophical arguments both ways on this one. Given our cooperative management there is an argument to having spanning tree there to catch us if/when we screw up. In a very tightly managed situation where there can be no loops then there is an argument to turn-off spanning tree, but god help you if there ever is a loop. -- ================================================ 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

Feb. 19, 2014

Re: Mice Issues

by Dan Boehlke

I was just thinking that, because generally exchange point best practice is to turn spanning tree off. So maybe I shouldn't be embarrassed for not having done it.... :-( -- Dan B. On Feb 19, 2014, at 5:43 PM, Richard Laager <rlaager(a)wiktel.com> wrote: > On Wed, 2014-02-19 at 17:40 -0600, Dan Boehlke wrote: >> The Vaultas switch has been configured to participate in spanning-tree > > Is that really what we want? > > -- > Richard > > 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

Feb. 19, 2014