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 <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 <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 <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: > [image: aeronet-logo] <http://www.aeronetpr.com/> [image: inc500] > <https://www.inc.com/profile/aeronet> [image: fb-logo] > <https://www.facebook.com/aeronetpr/> [image: insta-logo] > <https://www.instagram.com/aeronetpr/?hl=en> [image: in-logo] > <https://www.linkedin.com/company/aeronet-broadband-corp> [image: > tw-logo] > <https://twitter.com/AeroNetPR?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor> > [image: yt-logo] > <https://www.youtube.com/channel/UCr2Q9WBrAYVm3Fn970Jd6VA> > www.aeronetpr.com | Metro Office Park #18 Suite 304 Guaynabo, PR 00968 > > *From: *AF <af-boun...@af.afmug.com> on behalf of Josh Baird < > joshba...@gmail.com> > *Reply-To: *AnimalFarm Microwave Users Group <af@af.afmug.com> > *Date: *Tuesday, December 31, 2019 at 11:41 AM > *To: *AnimalFarm Microwave Users Group <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 <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 <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 > > 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 <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 > >>> lesm...@ecsis.net > >>> > >>> -- > >>> 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 > > > -- > 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 > > -- > 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 >
-- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
