I can answer that question. Don't do it. Grey market gear will end up costing you almost as much as getting it used (possibly new) from a dealer. And the hoops you have to jump through to get software updates on grey market is obscene. You have pay several thousand to get it re-certified by Juniper to get into a service contract and then you have to pay for the service contract.
-- Christopher Tyler Senior Network Engineer MTCRE/MTCNA/MTCTCE/MTCWE Total Highspeed Internet Solutions 1091 W. Kathryn Street Nixa, MO 65714 (417) 851-1107 x. 9002 www.totalhighspeed.com ----- Original Message ----- > From: "Josh Baird" <joshba...@gmail.com> > To: "AnimalFarm Microwave Users Group" <af@af.afmug.com> > Sent: Saturday, January 4, 2020 4:06:56 PM > Subject: Re: [AFMUG] Juniper routers > In some ways, Juniper isn't any better than Cisco in terms of licensed > software > features and it seems to only be getting worse. Some features (on *some* > platforms) are honor based, but lots are not and require a license. You can > purchase licenses from any Juniper reseller. I'm not sure what the process is > for getting J-Care on used/grey-market gear, as I have never tried to do that. > > You need an active support contract in order to download software from their > website, although it's not as restrictive as Cisco's which now requires you to > have a contract on a specific device to get firmware for that device iirc. > > On Sat, Jan 4, 2020 at 4:45 PM Forrest Christian (List Account) < [ > mailto:li...@packetflux.com | li...@packetflux.com ] > wrote: > > > > Seems like a good question to ask the burning question I've had about juniper > and specifically how juniper deals with license/firmware updates, etc. > > We've been a cisco shop since day one. Over the years they've gotten more and > more aggressive with their licensing requirements and controlled access to > firmware updates. At this point they seem to care less about selling hardware > and are more about extracting as much license and support revenue as possible > which makes picking up a used router a much riskier proposition. > > How does juniper handle this type of stuff, especially in relation to used > gear? > And in the context of getting the right software features (bgp, reasonable > number of ospf routes, etc) enabled. And so on. > > On Tue, Dec 31, 2019, 7:39 PM Mark Radabaugh < [ mailto:m...@amplex.net | > m...@amplex.net ] > wrote: > > > > Not necessarily. Depending on model many have redundant routing engines, > multiple power supplies, fan trays, etc. You may want to have spare cards and > possibly a empty chassis in the really odd event of a backplane issue. All > depends on you risk tolerance. > > Mark > > Mark Radabaugh > Amplex > 22690 Pemberville Rd > Luckey, OH 43443 > 419-261-5996 > > > > On Dec 31, 2019, at 9:18 PM, Jon Langeler < [ > mailto:jon-ispli...@michwave.net | > jon-ispli...@michwave.net ] > wrote: > > > > > Does one have to buy two of these for redundancy as we do with our current but > smaller routers? > > Jon Langeler > Michwave Technologies, Inc. > > > > > On Dec 31, 2019, at 11:11 AM, Gino A. Villarini < [ mailto:g...@aeronetpr.com > | > g...@aeronetpr.com ] > wrote: > > > > > > > Can go wrong with juniper.. I’ll vouch for the MX204’s great units. Our Core > is > MX480 soon to be upgraded to MX10003 > > > > Gino Villarini > Founder/President > @gvillarini > t: 787.273.4143 Ext. 204 > m: > [ http://www.aeronetpr.com/ ] [ https://www.inc.com/profile/aeronet ] > [ > https://www.facebook.com/aeronetpr/ ] [ > https://www.instagram.com/aeronetpr/?hl=en ] [ > https://www.linkedin.com/company/aeronet-broadband-corp ] [ > https://twitter.com/AeroNetPR?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor > ] [ https://www.youtube.com/channel/UCr2Q9WBrAYVm3Fn970Jd6VA ] [ > http://www.aeronetpr.com/ | www.aeronetpr.com ] | Metro Office Park #18 Suite > 304 Guaynabo, PR 00968 > > > > > From: AF < [ mailto:af-boun...@af.afmug.com | af-boun...@af.afmug.com ] > on > behalf of Josh Baird < [ mailto:joshba...@gmail.com | joshba...@gmail.com ] > > Reply-To: AnimalFarm Microwave Users Group < [ mailto:af@af.afmug.com | > af@af.afmug.com ] > > Date: Tuesday, December 31, 2019 at 11:41 AM > To: AnimalFarm Microwave Users Group < [ mailto:af@af.afmug.com | > af@af.afmug.com ] > > Subject: Re: [AFMUG] Juniper routers > > > > > > Overall, the JunOS syntax is far more powerful and nicer to use (once you > learn > it) than IOS in my opinion. > > > > > > On Tue, Dec 31, 2019 at 10:17 AM Mark Radabaugh < [ mailto:m...@amplex.net | > m...@amplex.net ] > wrote: > > > > > Syntax is a different but there are a lot of things you will like compared to > the older IOS versions. ‘commit confirmed 5’ alone is worth changing for. > > Mark > >> On Dec 31, 2019, at 8:43 AM, Larry Smith < [ mailto:lesm...@ecsis.net | >> lesm...@ecsis.net ] > wrote: >> >> This first one will replace our primary backbone router >> >> Mainly just curious what my learning curve is going to be >> and if there were "resources" here to help when I shoot >> myself in the foot. >> >> -- >> Larry Smith >> [ mailto:lesm...@ecsis.net | lesm...@ecsis.net ] >> >> On Mon December 30 2019 16:28, Josh Baird wrote: >>> Several people here use Juniper. >>> >>> What role are you putting the MX240 in? What would you like to know? >>> >>> On Mon, Dec 30, 2019 at 5:13 PM Larry Smith < [ mailto:lesm...@ecsis.net | >>> lesm...@ecsis.net ] > wrote: >>>> Curiousity question. >>>> We are getting ready to replace our Cisco 7206-VXR G2 router >>>> with a Juniper MX240 and just wondering how many here actually >>>> use Juniper. Trying to do some reading and figure out what I am >>>> in for in the conversion. >>>> >>>> -- >>>> Larry Smith >>>> [ mailto:lesm...@ecsis.net | lesm...@ecsis.net ] >>>> >>>> -- >>>> AF mailing list >>>> [ mailto:AF@af.afmug.com | AF@af.afmug.com ] >>>> [ http://af.afmug.com/mailman/listinfo/af_af.afmug.com | > http://af.afmug.com/mailman/listinfo/af_af.afmug.com ] >> >> -- >> AF mailing list >> [ mailto:AF@af.afmug.com | AF@af.afmug.com ] >> [ http://af.afmug.com/mailman/listinfo/af_af.afmug.com | > http://af.afmug.com/mailman/listinfo/af_af.afmug.com ] > > > -- > AF mailing list > [ mailto:AF@af.afmug.com | AF@af.afmug.com ] > [ http://af.afmug.com/mailman/listinfo/af_af.afmug.com | > http://af.afmug.com/mailman/listinfo/af_af.afmug.com ] > -- > AF mailing list > [ mailto:AF@af.afmug.com | AF@af.afmug.com ] > [ http://af.afmug.com/mailman/listinfo/af_af.afmug.com | > http://af.afmug.com/mailman/listinfo/af_af.afmug.com ] > -- > AF mailing list > [ mailto:AF@af.afmug.com | AF@af.afmug.com ] > [ http://af.afmug.com/mailman/listinfo/af_af.afmug.com | > http://af.afmug.com/mailman/listinfo/af_af.afmug.com ] > -- > AF mailing list > [ mailto:AF@af.afmug.com | AF@af.afmug.com ] > [ http://af.afmug.com/mailman/listinfo/af_af.afmug.com | > http://af.afmug.com/mailman/listinfo/af_af.afmug.com ] > -- > AF mailing list > [ mailto:AF@af.afmug.com | AF@af.afmug.com ] > [ http://af.afmug.com/mailman/listinfo/af_af.afmug.com | > http://af.afmug.com/mailman/listinfo/af_af.afmug.com ] > > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com -- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
