- mice-discuss - lists.micemn.net

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

by Levi Pederson

Kudos to Anthony as well. Thank you, *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipederson(a)mankatonetworks.net On Thu, Oct 27, 2016 at 1:29 PM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > On Thu, Oct 27, 2016 at 07:03:41AM -0500, Mike O'Connor wrote: > > i think we owe you one, Doug > > > > thanks! > > No problem. Anthony was there too checking out things and helping, > so thanks out to him too. > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades >

Oct. 27, 2016

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

by Doug McIntyre

On Thu, Oct 27, 2016 at 07:03:41AM -0500, Mike O'Connor wrote: > i think we owe you one, Doug > > thanks! No problem. Anthony was there too checking out things and helping, so thanks out to him too. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 27, 2016

Re: Peering with research orgs

by DeLong, Owen

I’m not entirely sure this is true in all cases. Owen On Oct 26, 2016, at 9:28 PM, Reid Fishler <rfishler(a)he.net<mailto:rfishler@he.net>> wrote: Just keep in mind we don't want to give away data that people are going to sell...unless we get something from it. Reid On Thu, Oct 27, 2016 at 12:15 AM, Richard Laager <rlaager(a)wiktel.com<mailto:rlaager@wiktel.com>> wrote: On 10/26/2016 11:07 PM, Frank Bulk wrote: > Does MICE have a policy regarding peering its router reflectors with research/data gathering orgs like Cymru, Dyn, Norse, ThousandEyes, QRator, etc. AFAIK, no policy. Somewhat related: I peer with BGPmon.net<http://bgpmon.net>, which is not on your list. Apparently they have been acquired by OpenDNS since I last looked at their website. I'm not aware of Cymru having a data gathering thing. Do you have a link? I peer with their bogons, UTRS, and IXP services. The IXP one was just added today actually: https://www.team-cymru.org/IXP/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.team-2Dcymru.org_I…> When I turned it up, I saw they were missing the IP ranges used by MICE and several others, so I let them know. -- Richard -- 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.iphouse.net_cgi-2…>

Oct. 27, 2016

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

by Ryan Goldberg

Having been through exact same scenario with one of our datacenter stacks, I feel yah. Thank you On Oct 27, 2016, at 8:53 AM, Levi Pederson <levipederson(a)MANKATONETWORKS.NET<mailto:levipederson@MANKATONETWORKS.NET>> wrote: Doug, Thanks Doug for all the work and effort. Levi Pederson Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipederson(a)mankatonetworks.net<mailto:levipederson@mankatonetworks.net> [http://www.mankatonetworks.com/images/mn_logo_email.png] On Thu, Oct 27, 2016 at 8:42 AM, David Farmer <farmer(a)umn.edu<mailto:farmer@umn.edu>> wrote: +1 Thanks for the good work On Thu, Oct 27, 2016 at 7:03 AM, Mike O'Connor <mike(a)haven2.com<mailto:mike@haven2.com>> wrote: i think we owe you one, Doug thanks! m > On Oct 27, 2016, at 2:07 AM, Doug McIntyre <merlyn(a)iphouse.net<mailto:merlyn@iphouse.net>> wrote: > > On Thu, Oct 27, 2016 at 01:35:06AM -0500, Doug McIntyre wrote: >> On Mon, Oct 24, 2016 at 01:20:45PM -0500, Doug McIntyre wrote: >>> We're going to upgrade the core MICE 10G switches coming up this week >>> on Wednesday night/ Thursday morning at 12:30AM-1:00AM CDT on 27 October. >> >> The upgrade is NOT going as planned, and we discovered our maintenance >> support has run out again, and JTAC will not help us (even at a pay >> per-incidence event). In fact, since the EX4500 has reached EOL, (although >> not EOM), and we let the contract expire, Juniper says we will be unable to >> renew maintenance support on the EX4500 at all. >> >> I'm looking at ways to bring the VC cluster fully back online now. >> >> If it comes down to it, I should have non-production hardware that could >> temporarily go in. > > Okay, I'm going to have to drive in. > > Right now, the state of things. > > The primary boot partition on the EX4500 took a digger, so we have bad > hardware. I was able to boot off the backup boot partition on the > EX4500, but this is still the older software version since I was in > the middle of the upgrade and the upgrade process didn't get to the > 2nd partition to upgrade it yet. > > The virtual chassis is now split version, which means VC won't work. > > Furthmore, networking is not working on either unit, even to the OOB. > > I am going to have to drive in to be physically in front of the box. > > I have two plans of attack. I will put the install image on a USB > drive and load it off USB onto the unit. IIRC, having done this > before long ago, this takes *ages* to do. > > If I can get both units happy with the same software versions, VC can > reestablish, and things can go along. > > I also have two EX4550's not-in-production right now, I'll bring them > along just in case. If things are really to the point of no return on > the EX4500, I can put in one or two and bring them up, restoring the > saved configs onto them. Of course, things will have to shuffle a little > then. This will delay me a bit in unmounting them from where they are, > but I think it is a safe backup plan. > > Another option would be to make the EX4550 standalone, but I have to > unhook the VC cables before this can happen, and it only helps along > a portion of the members. I don't think this is worthwhile to pursue. > > So, it'll be another hour before I can get downtown to my place, get > hardware, and get over to 511. > > -- > Doug McIntyre <merlyn(a)iphouse.net<mailto:merlyn@iphouse.net>> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades WI:(715) 598-4284<tel:%28715%29%20598-4284> MN:(651) 647-6109<tel:%28651%29%20647-6109> Toll Free:(800) 896-0907<tel:%28800%29%20896-0907> Fax:(866)-280-2356<tel:%28866%29-280-2356> -- =============================================== David Farmer Email:farmer@umn.edu<mailto:Email%3Afarmer@umn.edu> Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815<tel:612-626-0815> Minneapolis, MN 55414-3029 Cell: 612-812-9952<tel: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

Oct. 27, 2016

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

by Levi Pederson

Doug, Thanks Doug for all the work and effort. *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipederson(a)mankatonetworks.net On Thu, Oct 27, 2016 at 8:42 AM, David Farmer <farmer(a)umn.edu> wrote: > +1 Thanks for the good work > > On Thu, Oct 27, 2016 at 7:03 AM, Mike O'Connor <mike(a)haven2.com> wrote: > >> i think we owe you one, Doug >> >> thanks! >> >> m >> >> > On Oct 27, 2016, at 2:07 AM, Doug McIntyre <merlyn(a)iphouse.net> wrote: >> > >> > On Thu, Oct 27, 2016 at 01:35:06AM -0500, Doug McIntyre wrote: >> >> On Mon, Oct 24, 2016 at 01:20:45PM -0500, Doug McIntyre wrote: >> >>> We're going to upgrade the core MICE 10G switches coming up this week >> >>> on Wednesday night/ Thursday morning at 12:30AM-1:00AM CDT on 27 >> October. >> >> >> >> The upgrade is NOT going as planned, and we discovered our maintenance >> >> support has run out again, and JTAC will not help us (even at a pay >> >> per-incidence event). In fact, since the EX4500 has reached EOL, >> (although >> >> not EOM), and we let the contract expire, Juniper says we will be >> unable to >> >> renew maintenance support on the EX4500 at all. >> >> >> >> I'm looking at ways to bring the VC cluster fully back online now. >> >> >> >> If it comes down to it, I should have non-production hardware that >> could >> >> temporarily go in. >> > >> > Okay, I'm going to have to drive in. >> > >> > Right now, the state of things. >> > >> > The primary boot partition on the EX4500 took a digger, so we have bad >> > hardware. I was able to boot off the backup boot partition on the >> > EX4500, but this is still the older software version since I was in >> > the middle of the upgrade and the upgrade process didn't get to the >> > 2nd partition to upgrade it yet. >> > >> > The virtual chassis is now split version, which means VC won't work. >> > >> > Furthmore, networking is not working on either unit, even to the OOB. >> > >> > I am going to have to drive in to be physically in front of the box. >> > >> > I have two plans of attack. I will put the install image on a USB >> > drive and load it off USB onto the unit. IIRC, having done this >> > before long ago, this takes *ages* to do. >> > >> > If I can get both units happy with the same software versions, VC can >> > reestablish, and things can go along. >> > >> > I also have two EX4550's not-in-production right now, I'll bring them >> > along just in case. If things are really to the point of no return on >> > the EX4500, I can put in one or two and bring them up, restoring the >> > saved configs onto them. Of course, things will have to shuffle a little >> > then. This will delay me a bit in unmounting them from where they are, >> > but I think it is a safe backup plan. >> > >> > Another option would be to make the EX4550 standalone, but I have to >> > unhook the VC cables before this can happen, and it only helps along >> > a portion of the members. I don't think this is worthwhile to pursue. >> > >> > So, it'll be another hour before I can get downtown to my place, get >> > hardware, and get over to 511. >> > >> > -- >> > Doug McIntyre <merlyn(a)iphouse.net> >> > ~.~ ipHouse ~.~ >> > Network Engineer/Provisioning/Jack of all Trades >> >> WI:(715) 598-4284 MN:(651) 647-6109 Toll Free:(800) 896-0907 Fax: >> (866)-280-2356 >> > > > > -- > =============================================== > David Farmer Email:farmer@umn.edu > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Oct. 27, 2016

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

by David Farmer

+1 Thanks for the good work On Thu, Oct 27, 2016 at 7:03 AM, Mike O'Connor <mike(a)haven2.com> wrote: > i think we owe you one, Doug > > thanks! > > m > > > On Oct 27, 2016, at 2:07 AM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > > > > On Thu, Oct 27, 2016 at 01:35:06AM -0500, Doug McIntyre wrote: > >> On Mon, Oct 24, 2016 at 01:20:45PM -0500, Doug McIntyre wrote: > >>> We're going to upgrade the core MICE 10G switches coming up this week > >>> on Wednesday night/ Thursday morning at 12:30AM-1:00AM CDT on 27 > October. > >> > >> The upgrade is NOT going as planned, and we discovered our maintenance > >> support has run out again, and JTAC will not help us (even at a pay > >> per-incidence event). In fact, since the EX4500 has reached EOL, > (although > >> not EOM), and we let the contract expire, Juniper says we will be > unable to > >> renew maintenance support on the EX4500 at all. > >> > >> I'm looking at ways to bring the VC cluster fully back online now. > >> > >> If it comes down to it, I should have non-production hardware that could > >> temporarily go in. > > > > Okay, I'm going to have to drive in. > > > > Right now, the state of things. > > > > The primary boot partition on the EX4500 took a digger, so we have bad > > hardware. I was able to boot off the backup boot partition on the > > EX4500, but this is still the older software version since I was in > > the middle of the upgrade and the upgrade process didn't get to the > > 2nd partition to upgrade it yet. > > > > The virtual chassis is now split version, which means VC won't work. > > > > Furthmore, networking is not working on either unit, even to the OOB. > > > > I am going to have to drive in to be physically in front of the box. > > > > I have two plans of attack. I will put the install image on a USB > > drive and load it off USB onto the unit. IIRC, having done this > > before long ago, this takes *ages* to do. > > > > If I can get both units happy with the same software versions, VC can > > reestablish, and things can go along. > > > > I also have two EX4550's not-in-production right now, I'll bring them > > along just in case. If things are really to the point of no return on > > the EX4500, I can put in one or two and bring them up, restoring the > > saved configs onto them. Of course, things will have to shuffle a little > > then. This will delay me a bit in unmounting them from where they are, > > but I think it is a safe backup plan. > > > > Another option would be to make the EX4550 standalone, but I have to > > unhook the VC cables before this can happen, and it only helps along > > a portion of the members. I don't think this is worthwhile to pursue. > > > > So, it'll be another hour before I can get downtown to my place, get > > hardware, and get over to 511. > > > > -- > > Doug McIntyre <merlyn(a)iphouse.net> > > ~.~ ipHouse ~.~ > > Network Engineer/Provisioning/Jack of all Trades > > WI:(715) 598-4284 MN:(651) 647-6109 Toll Free:(800) 896-0907 Fax: > (866)-280-2356 > -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

Oct. 27, 2016

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

by Mike Horwath

On Thu, Oct 27, 2016 at 08:06:45AM -0500, Jason Hanke wrote: > There aren't enough ports on the 4550 to swap it in we would need > two. We are due for a fabric upgrade. EX4500 is 40 ports base, 48 ports with addon cards. EX4550 is 32 ports base, 48 ports with addon cards. Is the current EX4500 running with 40 ports or 48? Could a EX4550 be brought into the fabric with addon cards to match up? (not disagreeing about fabric upgrade though will be much easier once non-profit status is done and some of us can donate cleanly) -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Oct. 27, 2016

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

by Mike Horwath

On Thu, Oct 27, 2016 at 01:35:06AM -0500, Doug McIntyre wrote: > If it comes down to it, I should have non-production hardware that > could temporarily go in. Haven't read the rest of the thread yet. Thanks for your work, Doug. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Oct. 27, 2016

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

by Jason Hanke

There aren't enough ports on the 4550 to swap it in we would need two. We are due for a fabric upgrade. On Oct 27, 2016 7:23 AM, "Ben Wiechman" <ben.wiechman(a)arvig.com> wrote: > What would be the proposed solution? Replace the failing EX4500 with a > 4550? If so, what does one of those run? > > > Ben Wiechman > Network Engineer IV | Arvig > Direct: 320.256.0184 > Cell: 320.247.3224 > Office: 320.256.7471 > ben.wiechman(a)arvig.com > > On Thu, Oct 27, 2016 at 7:03 AM, Mike O'Connor <mike(a)haven2.com> wrote: > >> i think we owe you one, Doug >> >> thanks! >> >> m >> >> > On Oct 27, 2016, at 2:07 AM, Doug McIntyre <merlyn(a)iphouse.net> wrote: >> > >> > On Thu, Oct 27, 2016 at 01:35:06AM -0500, Doug McIntyre wrote: >> >> On Mon, Oct 24, 2016 at 01:20:45PM -0500, Doug McIntyre wrote: >> >>> We're going to upgrade the core MICE 10G switches coming up this week >> >>> on Wednesday night/ Thursday morning at 12:30AM-1:00AM CDT on 27 >> October. >> >> >> >> The upgrade is NOT going as planned, and we discovered our maintenance >> >> support has run out again, and JTAC will not help us (even at a pay >> >> per-incidence event). In fact, since the EX4500 has reached EOL, >> (although >> >> not EOM), and we let the contract expire, Juniper says we will be >> unable to >> >> renew maintenance support on the EX4500 at all. >> >> >> >> I'm looking at ways to bring the VC cluster fully back online now. >> >> >> >> If it comes down to it, I should have non-production hardware that >> could >> >> temporarily go in. >> > >> > Okay, I'm going to have to drive in. >> > >> > Right now, the state of things. >> > >> > The primary boot partition on the EX4500 took a digger, so we have bad >> > hardware. I was able to boot off the backup boot partition on the >> > EX4500, but this is still the older software version since I was in >> > the middle of the upgrade and the upgrade process didn't get to the >> > 2nd partition to upgrade it yet. >> > >> > The virtual chassis is now split version, which means VC won't work. >> > >> > Furthmore, networking is not working on either unit, even to the OOB. >> > >> > I am going to have to drive in to be physically in front of the box. >> > >> > I have two plans of attack. I will put the install image on a USB >> > drive and load it off USB onto the unit. IIRC, having done this >> > before long ago, this takes *ages* to do. >> > >> > If I can get both units happy with the same software versions, VC can >> > reestablish, and things can go along. >> > >> > I also have two EX4550's not-in-production right now, I'll bring them >> > along just in case. If things are really to the point of no return on >> > the EX4500, I can put in one or two and bring them up, restoring the >> > saved configs onto them. Of course, things will have to shuffle a little >> > then. This will delay me a bit in unmounting them from where they are, >> > but I think it is a safe backup plan. >> > >> > Another option would be to make the EX4550 standalone, but I have to >> > unhook the VC cables before this can happen, and it only helps along >> > a portion of the members. I don't think this is worthwhile to pursue. >> > >> > So, it'll be another hour before I can get downtown to my place, get >> > hardware, and get over to 511. >> > >> > -- >> > Doug McIntyre <merlyn(a)iphouse.net> >> > ~.~ ipHouse ~.~ >> > Network Engineer/Provisioning/Jack of all Trades >> >> WI:(715) 598-4284 MN:(651) 647-6109 Toll Free:(800) 896-0907 Fax: >> (866)-280-2356 >> > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Oct. 27, 2016

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

by Ben Wiechman

What would be the proposed solution? Replace the failing EX4500 with a 4550? If so, what does one of those run? Ben Wiechman Network Engineer IV | Arvig Direct: 320.256.0184 Cell: 320.247.3224 Office: 320.256.7471 ben.wiechman(a)arvig.com On Thu, Oct 27, 2016 at 7:03 AM, Mike O'Connor <mike(a)haven2.com> wrote: > i think we owe you one, Doug > > thanks! > > m > > > On Oct 27, 2016, at 2:07 AM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > > > > On Thu, Oct 27, 2016 at 01:35:06AM -0500, Doug McIntyre wrote: > >> On Mon, Oct 24, 2016 at 01:20:45PM -0500, Doug McIntyre wrote: > >>> We're going to upgrade the core MICE 10G switches coming up this week > >>> on Wednesday night/ Thursday morning at 12:30AM-1:00AM CDT on 27 > October. > >> > >> The upgrade is NOT going as planned, and we discovered our maintenance > >> support has run out again, and JTAC will not help us (even at a pay > >> per-incidence event). In fact, since the EX4500 has reached EOL, > (although > >> not EOM), and we let the contract expire, Juniper says we will be > unable to > >> renew maintenance support on the EX4500 at all. > >> > >> I'm looking at ways to bring the VC cluster fully back online now. > >> > >> If it comes down to it, I should have non-production hardware that could > >> temporarily go in. > > > > Okay, I'm going to have to drive in. > > > > Right now, the state of things. > > > > The primary boot partition on the EX4500 took a digger, so we have bad > > hardware. I was able to boot off the backup boot partition on the > > EX4500, but this is still the older software version since I was in > > the middle of the upgrade and the upgrade process didn't get to the > > 2nd partition to upgrade it yet. > > > > The virtual chassis is now split version, which means VC won't work. > > > > Furthmore, networking is not working on either unit, even to the OOB. > > > > I am going to have to drive in to be physically in front of the box. > > > > I have two plans of attack. I will put the install image on a USB > > drive and load it off USB onto the unit. IIRC, having done this > > before long ago, this takes *ages* to do. > > > > If I can get both units happy with the same software versions, VC can > > reestablish, and things can go along. > > > > I also have two EX4550's not-in-production right now, I'll bring them > > along just in case. If things are really to the point of no return on > > the EX4500, I can put in one or two and bring them up, restoring the > > saved configs onto them. Of course, things will have to shuffle a little > > then. This will delay me a bit in unmounting them from where they are, > > but I think it is a safe backup plan. > > > > Another option would be to make the EX4550 standalone, but I have to > > unhook the VC cables before this can happen, and it only helps along > > a portion of the members. I don't think this is worthwhile to pursue. > > > > So, it'll be another hour before I can get downtown to my place, get > > hardware, and get over to 511. > > > > -- > > Doug McIntyre <merlyn(a)iphouse.net> > > ~.~ ipHouse ~.~ > > Network Engineer/Provisioning/Jack of all Trades > > WI:(715) 598-4284 MN:(651) 647-6109 Toll Free:(800) 896-0907 Fax: > (866)-280-2356 >

Oct. 27, 2016

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

by Mike O'Connor

i think we owe you one, Doug thanks! m > On Oct 27, 2016, at 2:07 AM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > > On Thu, Oct 27, 2016 at 01:35:06AM -0500, Doug McIntyre wrote: >> On Mon, Oct 24, 2016 at 01:20:45PM -0500, Doug McIntyre wrote: >>> We're going to upgrade the core MICE 10G switches coming up this week >>> on Wednesday night/ Thursday morning at 12:30AM-1:00AM CDT on 27 October. >> >> The upgrade is NOT going as planned, and we discovered our maintenance >> support has run out again, and JTAC will not help us (even at a pay >> per-incidence event). In fact, since the EX4500 has reached EOL, (although >> not EOM), and we let the contract expire, Juniper says we will be unable to >> renew maintenance support on the EX4500 at all. >> >> I'm looking at ways to bring the VC cluster fully back online now. >> >> If it comes down to it, I should have non-production hardware that could >> temporarily go in. > > Okay, I'm going to have to drive in. > > Right now, the state of things. > > The primary boot partition on the EX4500 took a digger, so we have bad > hardware. I was able to boot off the backup boot partition on the > EX4500, but this is still the older software version since I was in > the middle of the upgrade and the upgrade process didn't get to the > 2nd partition to upgrade it yet. > > The virtual chassis is now split version, which means VC won't work. > > Furthmore, networking is not working on either unit, even to the OOB. > > I am going to have to drive in to be physically in front of the box. > > I have two plans of attack. I will put the install image on a USB > drive and load it off USB onto the unit. IIRC, having done this > before long ago, this takes *ages* to do. > > If I can get both units happy with the same software versions, VC can > reestablish, and things can go along. > > I also have two EX4550's not-in-production right now, I'll bring them > along just in case. If things are really to the point of no return on > the EX4500, I can put in one or two and bring them up, restoring the > saved configs onto them. Of course, things will have to shuffle a little > then. This will delay me a bit in unmounting them from where they are, > but I think it is a safe backup plan. > > Another option would be to make the EX4550 standalone, but I have to > unhook the VC cables before this can happen, and it only helps along > a portion of the members. I don't think this is worthwhile to pursue. > > So, it'll be another hour before I can get downtown to my place, get > hardware, and get over to 511. > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades WI:(715) 598-4284 MN:(651) 647-6109 Toll Free:(800) 896-0907 Fax:(866)-280-2356

Oct. 27, 2016

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

by Doug McIntyre

On Thu, Oct 27, 2016 at 02:07:46AM -0500, Doug McIntyre wrote: > On Thu, Oct 27, 2016 at 01:35:06AM -0500, Doug McIntyre wrote: > > On Mon, Oct 24, 2016 at 01:20:45PM -0500, Doug McIntyre wrote: > > > We're going to upgrade the core MICE 10G switches coming up this week > > > on Wednesday night/ Thursday morning at 12:30AM-1:00AM CDT on 27 October. > > > > The upgrade is NOT going as planned.. The USB recovery did go as planned, so the 4500 is back up, the 4500 and 4550 are VC'd together, and everything is looking good pingwise, trafficwise, so I brought up BGP for everybody again as well. Traffic is picking up across the Exchange. I see lots of routes, especially from HE, so things should be picking up for everybody. Anthony and I have checked out a lot of members traffic levels and they look like they are returning to normal ranges. We're calling it a night. End result, we are up to date on software, everything should be normalled up, and now we have to determine what to do about end of life, semi-broken hardware that is the 4500 box. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 27, 2016

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

by Doug McIntyre

On Thu, Oct 27, 2016 at 01:35:06AM -0500, Doug McIntyre wrote: > On Mon, Oct 24, 2016 at 01:20:45PM -0500, Doug McIntyre wrote: > > We're going to upgrade the core MICE 10G switches coming up this week > > on Wednesday night/ Thursday morning at 12:30AM-1:00AM CDT on 27 October. > > The upgrade is NOT going as planned, and we discovered our maintenance > support has run out again, and JTAC will not help us (even at a pay > per-incidence event). In fact, since the EX4500 has reached EOL, (although > not EOM), and we let the contract expire, Juniper says we will be unable to > renew maintenance support on the EX4500 at all. > > I'm looking at ways to bring the VC cluster fully back online now. > > If it comes down to it, I should have non-production hardware that could > temporarily go in. Okay, I'm going to have to drive in. Right now, the state of things. The primary boot partition on the EX4500 took a digger, so we have bad hardware. I was able to boot off the backup boot partition on the EX4500, but this is still the older software version since I was in the middle of the upgrade and the upgrade process didn't get to the 2nd partition to upgrade it yet. The virtual chassis is now split version, which means VC won't work. Furthmore, networking is not working on either unit, even to the OOB. I am going to have to drive in to be physically in front of the box. I have two plans of attack. I will put the install image on a USB drive and load it off USB onto the unit. IIRC, having done this before long ago, this takes *ages* to do. If I can get both units happy with the same software versions, VC can reestablish, and things can go along. I also have two EX4550's not-in-production right now, I'll bring them along just in case. If things are really to the point of no return on the EX4500, I can put in one or two and bring them up, restoring the saved configs onto them. Of course, things will have to shuffle a little then. This will delay me a bit in unmounting them from where they are, but I think it is a safe backup plan. Another option would be to make the EX4550 standalone, but I have to unhook the VC cables before this can happen, and it only helps along a portion of the members. I don't think this is worthwhile to pursue. So, it'll be another hour before I can get downtown to my place, get hardware, and get over to 511. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 27, 2016

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

by Doug McIntyre

On Mon, Oct 24, 2016 at 01:20:45PM -0500, Doug McIntyre wrote: > We're going to upgrade the core MICE 10G switches coming up this week > on Wednesday night/ Thursday morning at 12:30AM-1:00AM CDT on 27 October. The upgrade is NOT going as planned, and we discovered our maintenance support has run out again, and JTAC will not help us (even at a pay per-incidence event). In fact, since the EX4500 has reached EOL, (although not EOM), and we let the contract expire, Juniper says we will be unable to renew maintenance support on the EX4500 at all. I'm looking at ways to bring the VC cluster fully back online now. If it comes down to it, I should have non-production hardware that could temporarily go in. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 27, 2016

Re: Peering with research orgs

by David Farmer

On Wed, Oct 26, 2016 at 11:07 PM, Frank Bulk <fbulk(a)mypremieronline.com> wrote: > Does MICE have a policy regarding peering its router reflectors with > research/data gathering orgs like Cymru, Dyn, Norse, ThousandEyes, QRator, > etc. A number of MICE participants peer with various of these and other services from their own networks, exposing some or all of the routes available through MICE to many of those services, at least indirectly. Do you see a particular advantage to MICE's participants, or the Internet, by making MICE's routes more directly available to such projects? Thanks -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

Oct. 27, 2016

Re: Peering with research orgs

by Richard Laager

On 10/27/2016 12:20 AM, David Farmer wrote: > ARIN documents the IXP assignment it makes at the following; > > https://www.arin.net/knowledge/micro_allocations.html Thanks! I've brought that to the attention of Team Cymru too. -- Richard

Oct. 27, 2016

Re: Peering with research orgs

by David Farmer

On Wed, Oct 26, 2016 at 11:15 PM, Richard Laager <rlaager(a)wiktel.com> wrote: > On 10/26/2016 11:07 PM, Frank Bulk wrote: > > Does MICE have a policy regarding peering its router reflectors with > research/data gathering orgs like Cymru, Dyn, Norse, ThousandEyes, QRator, > etc. > > AFAIK, no policy. > > Somewhat related: > > I peer with BGPmon.net, which is not on your list. Apparently they have > been acquired by OpenDNS since I last looked at their website. > > I'm not aware of Cymru having a data gathering thing. Do you have a > link? I peer with their bogons, UTRS, and IXP services. > > The IXP one was just added today actually: > https://www.team-cymru.org/IXP/ > > When I turned it up, I saw they were missing the IP ranges used by MICE > and several others, so I let them know. > FYI, ARIN documents the IXP assignment it makes at the following; https://www.arin.net/knowledge/micro_allocations.html -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

Oct. 27, 2016

Re: Peering with research orgs

by Reid Fishler

Just keep in mind we don't want to give away data that people are going to sell...unless we get something from it. Reid On Thu, Oct 27, 2016 at 12:15 AM, Richard Laager <rlaager(a)wiktel.com> wrote: > On 10/26/2016 11:07 PM, Frank Bulk wrote: > > Does MICE have a policy regarding peering its router reflectors with > research/data gathering orgs like Cymru, Dyn, Norse, ThousandEyes, QRator, > etc. > > AFAIK, no policy. > > Somewhat related: > > I peer with BGPmon.net, which is not on your list. Apparently they have > been acquired by OpenDNS since I last looked at their website. > > I'm not aware of Cymru having a data gathering thing. Do you have a > link? I peer with their bogons, UTRS, and IXP services. > > The IXP one was just added today actually: > https://www.team-cymru.org/IXP/ > > When I turned it up, I saw they were missing the IP ranges used by MICE > and several others, so I let them know. > > -- > Richard > > -- Reid Fishler Director Hurricane Electric +1-510-580-4178

Oct. 27, 2016

Re: Peering with research orgs

by Richard Laager

On 10/26/2016 11:07 PM, Frank Bulk wrote: > Does MICE have a policy regarding peering its router reflectors with research/data gathering orgs like Cymru, Dyn, Norse, ThousandEyes, QRator, etc. AFAIK, no policy. Somewhat related: I peer with BGPmon.net, which is not on your list. Apparently they have been acquired by OpenDNS since I last looked at their website. I'm not aware of Cymru having a data gathering thing. Do you have a link? I peer with their bogons, UTRS, and IXP services. The IXP one was just added today actually: https://www.team-cymru.org/IXP/ When I turned it up, I saw they were missing the IP ranges used by MICE and several others, so I let them know. -- Richard

Oct. 27, 2016

Peering with research orgs

by Frank Bulk

Does MICE have a policy regarding peering its router reflectors with research/data gathering orgs like Cymru, Dyn, Norse, ThousandEyes, QRator, etc. Frank

Oct. 27, 2016

Re: BFD support on BGP sessions

by Doug McIntyre

On Tue, Oct 25, 2016 at 02:11:20PM -0500, Andrew Hoyos wrote: > Looks as expected here. Thanks for getting this set up on rs1. > Maybe let buck for a few days and we can confirm no issues on either side? Yep, I'll let it run, and check on it and announce it to the list for whoever wants to, and then see if we want to default to everybody. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 25, 2016

Re: MICE Port Runout

by Andrew Hoyos

Also, just a note on this for those thinking in 501(c)3 lines. My understanding of a 501(c)6 is that the donations/contributions from outside parties to MICE are *not* tax deductible for the contributor. https://www.irs.gov/charities-non-profits/other-non-profits/tax-treatment-o… -- Andrew Hoyos hoyosa(a)gmail.com > On Oct 24, 2016, at 9:56 PM, Larry Patterson <larry(a)atomicdata.com> wrote: > > So assuming paperwork happens in a timely fashion, donations after the filing date would be tax deductible for 2016? Is that the agreed upon direction? If so, I would suggest we get some end of year charitable giving going on. I would be interested in participating. What do the lawyers say about 2016 vs. 2017 status? > > Sent from my iPhone > > > > > > > > > > > > > > > > > > > > > > Larry Patterson > Chief Technology Officer > ---- > Atomic Data® // Safe. Simple. Smart.™ > 615 North 3rd Street > Minneapolis, MN 55401 > Main // 612.466.2000 > Direct // 612.466.2080 > > It's official. We're SOC 3 Certified, again! > > > > On Oct 24, 2016, at 21:47, Richard Laager <rlaager(a)WIKTEL.COM> wrote: > > > >> On 10/24/2016 08:54 PM, Larry Patterson wrote: > >> Is MICE a non-profit yet or will it be by End of year? > > > > Not yet, and I can't guarantee it. > > > > I'm currently waiting on the Minnesota Secretary of State's office to > > accept a filing. I expected it to be done last week. I'm doing some > > overnight maintenance, so my schedule is off-cycle of normal business > > hours. I've emailed them just now to inquire about the status. > > > > Once that is done, I'll request certified copies, which I expect to take > > a few days. Assuming the rest of the board has no objections, I'll sign > > and file the IRS form. > > > > I'm gone for a couple weeks starting next week. So this may get delayed > > until I'm back. But worst case, this really should be mailed to the IRS > > no later than November 18th. > > > > -- > > Richard > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Oct. 25, 2016

Re: Please welcome Fastly to MICE!

by Levi Pederson

Andrew, We have an IXP Manager (they just simplified their install a great deal) setup running now for just the metrics. Except for bursty MAX bits feeds it's pretty good (Real max of 25, system shows full burst max at 28 still working on why it's less consistent than our cacti). I am going to attempt a roll out of the Route Servers config additions in the next couple of weekends. Thank you, *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipederson(a)mankatonetworks.net On Tue, Oct 25, 2016 at 2:05 PM, Andrew Hoyos <hoyosa(a)gmail.com> wrote: > The folks on NWAX are using IXPManager (https://github.com/inex/IXP- > Manager), as well as others. AFAIK, this automates lots of this process > (DNS, route-servers, etc) and pulls things from PeeringDB. > Might be worth a look. > > -- > Andrew Hoyos > hoyosa(a)gmail.com > > > > > On Oct 25, 2016, at 2:00 PM, Jason Hanke <jayhanke(a)NEUTRALPATH.NET> > wrote: > > > > There is also a peeringDB API. > > > > It might be time for a database driven documentation. Then we could > > export/import to dns or switch configs. > > > > An online request form might be a good start. > > > > On Tue, Oct 25, 2016 at 1:56 PM, Richard Laager <rlaager(a)wiktel.com> > wrote: > >> The exchange only cares about the max prefix value if it's larger than > >> our default route server limit of 1000. That's a big network, and I > >> think we've only hit that once. I'm not sure we need to bother getting > >> an explicit number from every network on turn-up. > >> > >> On the PeeringDB thing... I've thought about that before too. Is > >> *requiring* an entry going too far? I'm on the fence about that. > >> > >> I see that SIX links the AS number in the participants list to PeeringDB > >> rather than bgp.he.net. I like the bgp.he.net links, but I should see > if > >> I can find some place on the list to put a PeeringDB link. > >> > >> -- > >> Richard > > > > > > > > -- > > 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. 25, 2016

Re: BFD support on BGP sessions

by Andrew Hoyos

On Oct 25, 2016, at 1:15 PM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > >> Sure, feel free to enable on the v6 sessions facing 53597, and I can >> fire up on this side and see if it works. > > Sure, I've added that to your IPv6 neighbor area. Looks as expected here. Thanks for getting this set up on rs1. hoyosa(a)er1.511.msp> show bfd session | match d1af 2001:504:27::d1af:0:1 Up xe-0/0/0.0 1.500 0.500 3 2001:504:27::d1af:0:2 Down xe-0/0/0.0 0.000 2.000 3 Maybe let buck for a few days and we can confirm no issues on either side? -- Andrew Hoyos hoyosa(a)gmail.com

Oct. 25, 2016

Re: Please welcome Fastly to MICE!

by Andrew Hoyos

The folks on NWAX are using IXPManager (https://github.com/inex/IXP-Manager) as well as others. AFAIK, this automates lots of this process (DNS, route-servers, etc) and pulls things from PeeringDB. Might be worth a look. -- Andrew Hoyos hoyosa(a)gmail.com > On Oct 25, 2016, at 2:00 PM, Jason Hanke <jayhanke(a)NEUTRALPATH.NET> wrote: > > There is also a peeringDB API. > > It might be time for a database driven documentation. Then we could > export/import to dns or switch configs. > > An online request form might be a good start. > > On Tue, Oct 25, 2016 at 1:56 PM, Richard Laager <rlaager(a)wiktel.com> wrote: >> The exchange only cares about the max prefix value if it's larger than >> our default route server limit of 1000. That's a big network, and I >> think we've only hit that once. I'm not sure we need to bother getting >> an explicit number from every network on turn-up. >> >> On the PeeringDB thing... I've thought about that before too. Is >> *requiring* an entry going too far? I'm on the fence about that. >> >> I see that SIX links the AS number in the participants list to PeeringDB >> rather than bgp.he.net. I like the bgp.he.net links, but I should see if >> I can find some place on the list to put a PeeringDB link. >> >> -- >> Richard > > > > -- > 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. 25, 2016