r 2.5 years+ and no issues.
>
> Happy to share if ever you want to refine your solution.
>
> Br,
> Niall
>
> -Original Message-
> From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf
> Of
> Philippe Girard
> Sent: 29 June 2018 15:15
>
: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] VRF export/import of eBGP learned route
Hello everyone
Thank you so much for your suggestions. The solution in this case is to
remove the autonomous-system statement completely from the routing-instance
routing-options and apply the local-as statement
Hello everyone
Thank you so much for your suggestions. The solution in this case is to
remove the autonomous-system statement completely from the routing-instance
routing-options and apply the local-as statement under bgp with the private
knob.
protocols {
bgp {
local-as 456 loops 2
Hello,
Does "no-prepend-global-as" help?
https://www.juniper.net/documentation/en_US/junos/topics/concept/bgp-local-as-introduction.html
HTH
Thx
Alex
On 29/06/2018 04:58, Aaron Gould wrote:
Use with caution in live environment as I'm going off of some testing I was
recently doing in my
I don't see this issue. Does it only happen when you have a different ASN
inside the VRF?
On Thu, Jun 28, 2018 at 10:44:07PM -0400, Philippe Girard wrote:
> Grettings
>
> I'm setting up this VRF that hosts the full routing table. I have other
> peerings or remote PEs that import IX routes
Use with caution in live environment as I'm going off of some testing I was
recently doing in my lab and I'm pretty sure I saw this same issue.
Sounds like something I saw with my internet boundary pe's, would add my AS
on routes were learned from internet and send as vpnv4 routes into my
Grettings
I'm setting up this VRF that hosts the full routing table. I have other
peerings or remote PEs that import IX routes through eBGP as well.
The problem resides on something TAC tells me is Juniper specific, which is
to add my own internal ASN to the as-path when using vrf-import to get
7 matches
Mail list logo
