The key is to make your network modular so you can swap out Cisco for Juniper or Juniper for Cisco or whatever the flavor of router/switch you may like at that point in time. Try not to get tied to an ecosystem.
Justin Wilson [email protected] — https://j2sw.com (AS399332) https://blog.j2sw.com - Podcast and Blog > On Jan 23, 2024, at 10:45 AM, <[email protected]> <[email protected]> > wrote: > > I started on Cisco forever ago. During my WISP times it was a blend of > Mikrotiks and refurb Cisco’s. > I started on Juniper a few years ago. It was alien at first, but I learned > to like it. Networks are never homogenous….at least not forever. > And after 25 years of scripting, programming, system admin, network > engineering, etc I have had to learn a lot of different syntax so I don’t see > a problem adding one more to the mix. I wouldn’t have a lot of sympathy for > an employee who’s stuck on Juniper or Cisco and doesn’t want to do the other. > > Call me crazy if you want. > > > From: AF <[email protected]> On Behalf Of Peter Kranz via AF > Sent: Monday, January 22, 2024 1:51 PM > To: 'AnimalFarm Microwave Users Group' <[email protected]> > Cc: Peter Kranz <[email protected]> > Subject: Re: [AFMUG] Used Juniper > > Juniper has an entirely different programming style that Cisco.. most network > folks like one or the other, I would not suggest mixing them in your network. > > Peter Kranz > www.UnwiredLtd.com <http://www.unwiredltd.com/> > Desk: 510-868-1614 x100 > Mobile: 510-207-0000 > [email protected] <mailto:[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
