March 2015 - mice-discuss - lists.micemn.net

Re: Route Reflectors swap out.

by Matthew Beckwell

I think the general consensus during the last discussion was "as long as we know ahead of time". Doug's notification certainly meets that criteria for me, and the MOP sounds solid. (Although I will still probably shut down my sessions the night before). ~Matthew On Tue, Mar 31, 2015 at 12:12 PM, Justin Krejci <JKrejci(a)usinternet.com> wrote: > Speaking for myself, any time is just fine as long as it is only one > server at a time, as you indicated. > > > ________________________________________ > From: MICE Discuss [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] on behalf of Doug > McIntyre [merlyn(a)IPHOUSE.NET] > Sent: Tuesday, March 31, 2015 11:50 AM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] Route Reflectors swap out. > > I should schedule up a time when I swap out the RR's with the new hardware. > I have them ready, just need to get them there at online. > > Of course I'd do one at a time, probably take down #2 first, and then > once that is up, and give it 15 mins to settle, go and down #1. > > Would the afternoon of Friday, 4/3/2015 work for people? > Should be a 30-45 minute procedure, it should be straight forward. > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades >

March 31, 2015

Re: Route Reflectors swap out.

by Justin Krejci

Speaking for myself, any time is just fine as long as it is only one server at a time, as you indicated. ________________________________________ From: MICE Discuss [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] on behalf of Doug McIntyre [merlyn(a)IPHOUSE.NET] Sent: Tuesday, March 31, 2015 11:50 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Route Reflectors swap out. I should schedule up a time when I swap out the RR's with the new hardware. I have them ready, just need to get them there at online. Of course I'd do one at a time, probably take down #2 first, and then once that is up, and give it 15 mins to settle, go and down #1. Would the afternoon of Friday, 4/3/2015 work for people? Should be a 30-45 minute procedure, it should be straight forward. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

March 31, 2015

Route Reflectors swap out.

by Doug McIntyre

I should schedule up a time when I swap out the RR's with the new hardware. I have them ready, just need to get them there at online. Of course I'd do one at a time, probably take down #2 first, and then once that is up, and give it 15 mins to settle, go and down #1. Would the afternoon of Friday, 4/3/2015 work for people? Should be a 30-45 minute procedure, it should be straight forward. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

March 31, 2015

OT: exfo BV10-100-1000?

by Ryan Goldberg

Hi all, sorry for the OT but I can't think of a better group to ask this of. I rented an FTB-200 to dig in to some hairy stuff and they didn't ship the loopback thing (BV10-100-1000). I was wondering if anyone has one or has access to one that I could borrow in short order. Thanks in advance- Ryan 218-390-5485

March 28, 2015

Re: MICE UG 16

by Mike Horwath

On Tue, Mar 17, 2015 at 06:46:21AM -0500, Shaun Carlson wrote: > To clarify, 1300 Nicollett Mall is the correct address yeah, ah well. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

March 28, 2015

Re: FW: New gen route servers

by Mike Horwath

On Fri, Mar 27, 2015 at 11:04:36AM -0500, Anton Kapela wrote: > On Fri, Mar 27, 2015 at 10:25 AM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > > > I'm not sure SSD would bring much, so far it has been controller failures, > > and not disk failures. Everything has all been enterprise grade drives in > > every iteration. > > indeed - not much, but quite useful (if one doesn't like things > rolling slow) for when one rocks out w/ their / or /usr or whatnot on > a sync-mounted fs ;) Still wrong problem. Just sayin'. ZFS and UFS are vastly different with metadata updates anyway so it really isn't part of the problem you are trying to solve. BTW: Still trolling. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

March 28, 2015

Re: FW: New gen route servers

by Mike Horwath

On Fri, Mar 27, 2015 at 07:13:12AM -0500, Anton Kapela wrote: > (Chiming in because storage and OS nerding) > > Given the use case (safety > perf), perhaps the route server storage > would be best matched by something like a sync-mounted file system, > raid1 with no cache enabled, or read cache only with a forced > write-through? Overkill and wrong solution for the wrong, imaginary, problem. > A pair of SLC-type SSD's with ext3/4, or XFS mounted 'sync' atop a > write-through raid1 should still be entirely awesome and performant > for the job of booting an OS and loading route-server binaries, and > perhaps even soaking up a few syslog outputs...while being as 'safe' > as the hardware allows. This isn't Linux either. Cause. You don't need linux to be your every hammer for every nail. Cause that's my storage and OS nerding coming out. Wanna really go to town? GlusterFS with 3 nodes with replica=3 and one node not on same network. But that won't help the system from crashing because of potential firmware bugs going on as Doug has mentioned. That's the problem, not an issue of corrupted storage. In fact, as far as I know, there has been zero corruption of data during these periods of instability showing that FreeBSD rocks even when using ZFS and I bet would be just as stable with UFS. > If that sounds tempting, tell me where to fedex the ssd media & > caddy adapters :) SSDs always good though. BTW: I'm a troll. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

March 28, 2015

Re: MICE Governance Documents

by Jason Hanke

> > > Also, are we afraid of using the term "switch" instead of the generic term > "equipment?" Are there situations where there is member connectivity that > does not involve the use of a switch specifically? Are just preparing in > case ATM makes a move to over? 53 bytes FTW! > I could see someone potentially provide layer 1 type equipment (xWDM) to provide an extension. I don't really understand the use case of doing something remote with no attached members other than someone builds a remote and then hopes that someone connects in the future. -- 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

March 27, 2015

Re: MICE Governance Documents

by Richard Laager

Note that this about who can be a member, not who is a member. There's the separate step of electing or appointing. On Fri, 2015-03-27 at 20:40 +0000, Justin Krejci wrote: > I would suggest an amendment to your 1A and 1B proposals > section (ii) changed from > an operator of equipment providing approved indirect connections. > to > an operator of equipment providing approved indirect connections with > at least one active member connection I considered this. I originally went so far as to write "two or more". But in the end, I took it out as I don't think this matters. The Board shouldn't approve a switch that's not going to have any members. If they do and it turns out nobody connects, they can just de-approve it after a while. Also, they can hold up approving the switch operator's membership (separate from "approving the switch") until such time as there are connections behind the switch. If we were to adopt your proposal, I'd like to see it amended by striking the word "member". We should not assume that all connected networks are necessarily members. > Depending on how your legalese translates, this could cover a fiber > provider not otherwise associated with the exchange, eg a provider who > leases wave service or dark fiber to connect the 511 fabric to a > remote colo switch. With proposal 1A you could have both the switch > operator and the fiber owner as members. With proposal 1B you could > have the switch operator (unless it's an official MICE switch), the > fiber owner, and the colo facility all of which could be separate > companies. I considered this possibility. But, even if the fiber owner tries to claim they're eligible for membership, the Board/members need not appoint/elect them. > Also, are we afraid of using the term "switch" instead of the generic > term "equipment?" Are there situations where there is member > connectivity that does not involve the use of a switch specifically? > Are just preparing in case ATM makes a move to over? 53 bytes FTW! I believe CNS still connects remote participants. (Halstad Telphone Company is the example now. Wikstrom Telephone Company was connected this way in the past.) This is done by extending the MICE VLAN through the CNS network out to the remote participants. It is not the case (at least it wasn't for us) that the remote participants have purchased a layer 2 circuit to 511 that they can cross-connect to arbitrary destinations. So it's not that they have a presence in 511 and are connected to a single, identifiable "remote switch". Granted, CNS is directly connected, and also runs an identifiable remote switch, so this is moot for them. And it may not be likely to occur with another network. But, for another example that might be more likely.... Imagine a carrier neutral data center operator carries the MICE VLAN through their switching fabric, whether that's in one building or more than one around the metro area. They might very well not run an IP network that connects to MICE. -- Richard

March 27, 2015

Re: MICE Governance Documents

by Justin Krejci

Richard, I would suggest an amendment to your 1A and 1B proposals section (ii) changed from an operator of equipment providing approved indirect connections. to an operator of equipment providing approved indirect connections with at least one active member connection Depending on how your legalese translates, this could cover a fiber provider not otherwise associated with the exchange, eg a provider who leases wave service or dark fiber to connect the 511 fabric to a remote colo switch. With proposal 1A you could have both the switch operator and the fiber owner as members. With proposal 1B you could have the switch operator (unless it's an official MICE switch), the fiber owner, and the colo facility all of which could be separate companies. Also, are we afraid of using the term "switch" instead of the generic term "equipment?" Are there situations where there is member connectivity that does not involve the use of a switch specifically? Are just preparing in case ATM makes a move to over? 53 bytes FTW! ________________________________ From: MICE Discuss [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] on behalf of Richard Laager [rlaager(a)WIKTEL.COM] Sent: Friday, March 27, 2015 3:13 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE Governance Documents I would still like to see operators of remote switches (e.g. Mankato Networks) be allowed to be members. PROPOSAL 1A: In order to qualify for membership, a member shall be: (i) an operator of an Internet Protocol network which has one or more direct, or approved indirect, connections to Midwest Internet Cooperative Exchange LLC’s (the “Company”) switches; or (ii) an operator of equipment providing approved indirect connections. PROPOSAL 1B: [ If we feel it is important to allow for Cologix (and similar companies in the future) to be members, then... ] In order to qualify for membership, a member shall be: (i) an operator of an Internet Protocol network which has one or more direct, or approved indirect, connections to Midwest Internet Cooperative Exchange LLC’s (the “Company”) switches; (ii) an operator of equipment providing approved indirect connections; or (iii) an operator of a colocation data center in which the Company's switches are located. I'd like to see this sentence change: CURRENT: A member may be elected or appointed to membership by the Board. PROPOSAL 2A: A member may be elected or appointed to membership. PROPOSAL 2B: A member may be elected to membership by the members or appointed to membership by the Board. -- Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 27, 2015