What is particularly fun because of this is the recent development that cisco requires but does not sell smartnet contracts to obtain firmware for end of lifecycle hardware.
The newer still supported hardware is subject to their aggressive software key nightmares which requires expensive keys before it becomes useful. This combination has led me to the point of needing to move to something else in the near future. Probably juniper in the core at the minimum. On Sun, Jan 5, 2020, 9:46 AM Ken Hohhof <[email protected]> wrote: > I would buy a SmartNet contract for one device of each type, and then use > the FW on the others. Since Cisco refused to separate hardware and > software maintenance, and I never used the hardware part, I figured it was > fair. > > > > *From:* AF <[email protected]> *On Behalf Of *[email protected] > *Sent:* Sunday, January 5, 2020 10:53 AM > *To:* AnimalFarm Microwave Users Group <[email protected]> > *Subject:* Re: [AFMUG] Juniper routers > > > > Well, you gotta admit, we all have had 20 years of buying some cheap cisco > device and then getting all the software we wanted for our used expensive > cisco stuff. I always felt slightly guilty doing it that way but it seemed > to be the defacto way in the industry. I presume they allowed it to > stimulate the market in a particular way. > > > > *From:* Josh Baird > > *Sent:* Saturday, January 4, 2020 3:06 PM > > *To:* AnimalFarm Microwave Users Group > > *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) < > [email protected]> 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 <[email protected]> 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 <[email protected]> > 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 <[email protected]> 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 <[email protected]> on behalf of Josh Baird < > [email protected]> > *Reply-To: *AnimalFarm Microwave Users Group <[email protected]> > *Date: *Tuesday, December 31, 2019 at 11:41 AM > *To: *AnimalFarm Microwave Users Group <[email protected]> > *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 <[email protected]> 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 <[email protected]> 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 > > [email protected] > > > > 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 <[email protected]> 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 > >>> [email protected] > >>> > >>> -- > >>> AF mailing list > >>> [email protected] > >>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > > > -- > > AF mailing list > > [email protected] > > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > ------------------------------ > > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com >
-- AF mailing list [email protected] http://af.afmug.com/mailman/listinfo/af_af.afmug.com
