Re: [j-nsp] PE-CE BGP announcements

2019-03-07 Thread Jason Lixfeld
Thanks! There was in fact a catch-all reject policy higher up in the config hierarchy that I didn’t clue into. So now I see it with all policies removed, so I should be able to work backwards from here. Thanks again for the clue! > On Mar 7, 2019, at 3:46 PM, Olivier Benghozi > wrote: > >

Re: [j-nsp] PE-CE BGP announcements

2019-03-07 Thread Olivier Benghozi
Really sure of your export policy when removed from the neighbour (that is, any policy under the protocol or the group) ? show bgp neighbor exact-instance foo 10.108.35.254 | match export Any NO-EXPORT community attached on the route? > Le 7 mars 2019 à 20:04, Jason Lixfeld a écrit : > > My

Re: [j-nsp] PE-CE BGP announcements

2019-03-07 Thread Jason Lixfeld
Hi, No, 10.108.35.254 is in a different AS, not AS12345. > On Mar 7, 2019, at 2:44 PM, Michael Still wrote: > > Is this just a case of BGP loop prevention working as expected? If I > understand correctly you are learning it from AS12345 but also wish to > announce it to a diff neighbor in

Re: [j-nsp] PE-CE BGP announcements

2019-03-07 Thread Michael Still
Is this just a case of BGP loop prevention working as expected? If I understand correctly you are learning it from AS12345 but also wish to announce it to a diff neighbor in AS12345? If so then try 'as-override' option. On Thu, Mar 7, 2019 at 2:06 PM Jason Lixfeld wrote: > Hello, > > I’m

[j-nsp] PE-CE BGP announcements

2019-03-07 Thread Jason Lixfeld
Hello, I’m trying to work through solving why a BGP prefix 126.126.126.0/24 announced to pe2 in vrf foo isn’t announced to EBGP neighbour 10.108.35.254 on pe1 that is also in vrf foo. jlixfeld@pe1# run show route protocol bgp table foo.inet.0 126.126.126.0/24 foo.inet.0: 41 destinations, 51

Re: [j-nsp] Hyper Mode on MX

2019-03-07 Thread adamv0025
> Franz Georg Köhler > Sent: Thursday, March 7, 2019 11:46 AM > > On Thu, Mar 07, 2019 at 12:31:48PM +0100, Olivier Benghozi > wrote: > > By the way HyperMode is only useful if you expect some very high > > throughput with very small packets (none of the MPCs are linerate > > using very small

Re: [j-nsp] Hyper Mode on MX

2019-03-07 Thread Jackson, William
Junos Fusion is not supported when hyper-mode is enabled. -Original Message- From: juniper-nsp On Behalf Of Franz Georg Köhler Sent: 07 March 2019 12:46 To: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Hyper Mode on MX On Thu, Mar 07, 2019 at 12:31:48PM +0100, Olivier Benghozi

Re: [j-nsp] Hyper Mode on MX

2019-03-07 Thread Franz Georg Köhler
On Thu, Mar 07, 2019 at 12:31:48PM +0100, Olivier Benghozi wrote: > By the way HyperMode is only useful if you expect some very high > throughput with very small packets (none of the MPCs are linerate > using very small packets, but HyperMode brings it closer). Thanks. While we actually don't

Re: [j-nsp] Hyper Mode on MX

2019-03-07 Thread Olivier Benghozi
By the way HyperMode is only useful if you expect some very high throughput with very small packets (none of the MPCs are linerate using very small packets, but HyperMode brings it closer). Your Junirepresentative may show you a linerate performance/packet size graph with/without HyperMode to

Re: [j-nsp] Hyper Mode on MX

2019-03-07 Thread Nathan Ward
> On 7/03/2019, at 10:40 PM, Franz Georg Köhler wrote: > > Hello, > > I wonder if it is gererally a good idea to enable HyperMode on MX or if > there are reasons not do do so? > > We are currently running MX960 with FPC7.

[j-nsp] Hyper Mode on MX

2019-03-07 Thread Franz Georg Köhler
Hello, I wonder if it is gererally a good idea to enable HyperMode on MX or if there are reasons not do do so? We are currently running MX960 with FPC7. Best regards, Franz Georg Köhler ___ juniper-nsp mailing list juniper-nsp@puck.nether.net