- mice-discuss - lists.micemn.net

Packet loss issue update

by Jason Hanke

Do we have an update on the minor packet loss issue after all the upgrades have been completed? -- 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

Oct. 31, 2016

Cacti graph showing count of MICE peers and prefixes

by Frank Bulk

The Cacti graph showing the number of MICE peers and prefixes has been blank since September 28 around 3 pm. Is there a way to get that back? Frank

Oct. 29, 2016

Re: MICE core switch maintenance window - 10/27/2016 12:30AM-1:00AM CDT

by Doug McIntyre

On Fri, Oct 28, 2016 at 04:10:35PM +0000, Shaun Carlson wrote: > While I like the idea of having some sort of tech list for deep discussions amongst those with specific access, I think we also need to keep the open nature of the exchange in mind to ensure we're not accidentally excluding someone or creating barriers to communication and collaboration in the process. I actually have a MICE-TECH list already setup, and I feed the RANCID config diffs into it. I've restricted its' membership to just the tech committee and have generally pushed anybody that found it to go talk on MICE-DISCUSS anyway. There's hardly anything that happens on it other than config diffs. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 28, 2016

Re: MICE core switch maintenance window - 10/27/2016 12:30AM-1:00AM CDT

by Richard Laager

On 10/28/2016 11:10 AM, Shaun Carlson wrote: > While I like the idea of having some sort of tech list for deep > discussions amongst those with specific access, I think we also need to > keep the open nature of the exchange in mind to ensure we're not > accidentally excluding someone or creating barriers to communication and > collaboration in the process. The alternative is off-list emails, which is what already happens. A mailing list brings an archive. -- Richard

Oct. 28, 2016

Re: MICE core switch maintenance window - 10/27/2016 12:30AM-1:00AM CDT

by Mike Horwath

On Fri, Oct 28, 2016 at 04:10:35PM +0000, Shaun Carlson wrote: > While I like the idea of having some sort of tech list for deep > discussions amongst those with specific access, I think we also need > to keep the open nature of the exchange in mind to ensure we're not > accidentally excluding someone or creating barriers to communication > and collaboration in the process. My question in return: why can't those discussions happen on -DISCUSS? Just playing *advocate here. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Oct. 28, 2016

Re: MICE core switch maintenance window - 10/27/2016 12:30AM-1:00AM CDT

by Shaun Carlson

While I like the idea of having some sort of tech list for deep discussions amongst those with specific access, I think we also need to keep the open nature of the exchange in mind to ensure we're not accidentally excluding someone or creating barriers to communication and collaboration in the process. S Shaun Carlson Director of Information Technology | Arvig ph: (218) 346.8673 | em: shaun.carlson(a)arvig.com On Fri, Oct 28, 2016 at 9:57 AM -0500, "Richard Laager" <rlaager(a)wiktel.com> wrote: On 10/28/2016 09:45 AM, Mike Horwath wrote: > On Tue, Oct 25, 2016 at 01:56:32PM -0500, Richard Laager wrote: >> 3) asking for a MICE-TECH and/or MICE-OPS list be created (depending >> on whether we have distinct groups and what those people want). I >> expect at least one list will be closed to members only. > > Give the word and it can be done. > > Hell both could be done though they seem a little redundant in naming. :) There may be a need to have one list for people with actual access to the equipment and a separate list for another set of users. But before we go there, I need to have more discussions with people who might be on those lists. -- Richard

Oct. 28, 2016

Re: MICE core switch maintenance window - 10/27/2016 12:30AM-1:00AM CDT

by Andrew Hoyos

> On Oct 28, 2016, at 10:30 AM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > >> I have to assume that regardless they are expensive. > > Actually, I think the QFX5200-32C is pretty reasonable price, and I think one > to shoot for, although watch out pricing it as hardware & software are seperate > line items. But in some ways, that is good, as this application doesn't need > VxLAN and EVPN or all the fancy new things. QFX5100-48 can be had for 48 port 10g density as well for like $6k NFR with the right Juniper partner (hint hint). Depending on direction the group wants to go as far as a new fabric and timing, I may even have one we would be willing to donate to the cause. -- Andrew Hoyos hoyosa(a)gmail.com

Oct. 28, 2016

Re: MICE core switch maintenance window - 10/27/2016 12:30AM-1:00AM CDT

by Doug McIntyre

On Fri, Oct 28, 2016 at 09:53:02AM -0500, Mike Horwath wrote: > On Thu, Oct 27, 2016 at 02:07:39PM -0500, Doug McIntyre wrote: > > The QFX5200-32C can get into newer technologies like adding 25G/50G > > and 100G capable ports. Again using breakout cables to breakout ports > > into the "slower" speeds we are running, and can get into the range of > > 128 x 10GB ports with breakout cables in 1U. .. > I have to assume that regardless they are expensive. Actually, I think the QFX5200-32C is pretty reasonable price, and I think one to shoot for, although watch out pricing it as hardware & software are seperate line items. But in some ways, that is good, as this application doesn't need VxLAN and EVPN or all the fancy new things. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 28, 2016

Re: MICE core switch maintenance window - 10/27/2016 12:30AM-1:00AM CDT

by Mike Horwath

On Fri, Oct 28, 2016 at 09:57:19AM -0500, Richard Laager wrote: > There may be a need to have one list for people with actual access > to the equipment and a separate list for another set of users. But > before we go there, I need to have more discussions with people who > might be on those lists. Oh that idea was bandied about back in month-one of MICE. Once you have an idea just reach out to me. I maintain the MICE-* lists still (and Doug recently helped with something that had been missed. ewps) -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Oct. 28, 2016

Re: MICE core switch maintenance window - 10/27/2016 12:30AM-1:00AM CDT

by Richard Laager

On 10/28/2016 09:45 AM, Mike Horwath wrote: > On Tue, Oct 25, 2016 at 01:56:32PM -0500, Richard Laager wrote: >> 3) asking for a MICE-TECH and/or MICE-OPS list be created (depending >> on whether we have distinct groups and what those people want). I >> expect at least one list will be closed to members only. > > Give the word and it can be done. > > Hell both could be done though they seem a little redundant in naming. :) There may be a need to have one list for people with actual access to the equipment and a separate list for another set of users. But before we go there, I need to have more discussions with people who might be on those lists. -- Richard

Oct. 28, 2016