Re: Juniper configuration recommendations/BCP

["Forrest Christian (List Account)" <lists () packetflux com>]

I will say that so far I'm finding JunOS and the Juniper documentation to
be a welcome change.   In my other life I write networking/IoT code and
have done my fair share of unix (linux, freebsd, sunos, etc.)
administration over the years.  As a result, JunOS is feeling more natural
than some devices I've configured over the years.   Right now, It's just a
matter of learning where all the stones one has to turn over to make it
work well are...

Thanks to everyone for the answers so far.   It will take a bit for me to
dig through and process them..  I can also see that there are definitely
some gems I didn't know about.

On Thu, Oct 8, 2020 at 9:53 AM Paschal Masha <paschal.masha () 6by7 net> wrote:

> Above all, JUNOS makes sense when configuring, you literally the software
> gives you the feel of talking to the device. If your brain is programmed to
> be logically then all pieces and modes easily come to life and adaptation
> becomes a zero hustle.
>
>
>
> *Paschal Masha*
> Lead Network Engineer
> 6x7 Networks | 1 (831)325-0544
> Time Zone: PST
>
>
> On Thu, Oct 8, 2020 at 6:44 PM Justin Oeder <jcoeder () gmail com> wrote:
>
> > If you are an OSPF shop, Cisco AD is 110 for internal and external
> > routes.  Juniper is 10 for internal and 150 for external.  This can be
> > changed via an export (maybe import) policy on the OSPF protocol.
> >
> > There is no 'network' statement in the Junos world.  There are a few
> > different ways to solve this same problem.  Up to you how you do it.
> >
> > Routing engine protection is much easier.  A firewall filter on the
> > loopback interface.  Here is a sample.  This is really where your BCP
> > starts.
> >
> > https://github.com/jcoeder/juniper-configurations/blob/master/protect-re.txt
> >
> > Dynamic prefix-lists are pretty cool.  They allow you to create prefix-
> > list based on other sections of the configuration.
> >
> > # In this first statement we use wildcards surrounding a . as this is
> > the format of an IPv4 address.
> > set policy-options prefix-list BGP_PEERS_DYNAMIC apply-path "protocols
> > bgp group <*> neighbor <*.*>"
> >
> > # In this second statement we use wildcards surrounding a : as this is
> > the format of an IPv6 address.
> > set policy-options prefix-list BGP_PEERS_DYNAMIC_V6 apply-path
> > "protocols bgp group <*> neighbor <*:*>"
> >
> > Justin
> >
> > On Thu, 2020-10-08 at 03:37 -0600, Forrest Christian (List Account)
> > wrote:
> > > <ISP hat on>
> > > After nearly 30 years of being a cisco shop, I'm working on
> > > configuring our first pair of Juniper MX204's to replace our current
> > > provider-edge cisco.
> > >
> > > I've worked through enough of the Juniper documentation/books to have
> > > a fairly good handle on how to configure these, but I wanted to check
> > > with the list to see if there are any Juniper-Specific gotchas I
> > > might run into that isn't documented well.
> > >
> > > I've done a bit of googling and am either finding stuff that is
> > > largely Cisco-specific or which is generic - all of which I'm
> > > rather familiar with based on my past history.   Is there anything I
> > > should worry about which is Juniper-specific?
> > >
> > > --
> > > - Forrest

-- 
- Forrest