RPD was single threaded application until very recently, so your RSVP
would compete to access to single core with every other task. Perhaps
not huge deal if you are BGP free MPLS core, but if you are not, then
you're going to see massive improvement by running later JunOS with
multithreaded RPD, th
There's no one magic knob that fixes CPU spikes in an MPLS environment.
They're all different. What I change to optimize mine might knock your
network over in 5 minutes. You need to determine what is triggering the
churn before you can reasonable optimize it. Take a look at logs and see
what is cau
Yes I thought the FIB filter is a given on a RR,
But didn’t know about the “no-install” knob so using:
“set routing-options forwarding-table export ” –where the policy
is just ”from protocol bgp; then reject”
-so I guess then it’s the FIB filter –that does the trick and allows us to use
And we played a bit with colleagues and found third way, for me it seems the
best - use no-install for protocol families, which effectively disables
installing routes to forwarding table and somehow disables nexthop validation.
My config is now like this:
> show configuration protocols bgp
mtu-
Hi,
I’ve been doing some more testing with the following results:
The following configurations work:
1. family mpls is deactivated on em1 with routing-options rib inet.3 static
route 0.0.0.0/0 discard configured
2. family mpls is enabled on em1 with routing-options rib inet.3 static route
0.0.
> From: Ivan Ivanov [mailto:ivanov.i...@gmail.com]
> Sent: Thursday, September 13, 2018 10:58 AM
>
> Hi,
>
> There are a few different ways to resolve the MP-BGP routes on out of band
> Juniper RR. Depends on how flexible you want to be, one can use static route
> in inet.3, change of the resolut
I think 16.1 was first.
ps Haux|grep rpd should show multiple rpd lines.
Also
y...@r41.labxtx01.us.bb> show task io |match {
KRT IO task 0 0 0 0
0 {krtio-th}
krtio-th 0 0 0 0
0 {krtio-th}
k
Hi,
There are a few different ways to resolve the MP-BGP routes on out of band
Juniper RR. Depends on how flexible you want to be, one can use static
route in inet.3, change of the resolution or rib-groups copying the routes
form inet.0 to inet.3.
Using the static route will work even without fam
OK,
so this seems also perfectly OK in my vRR:
resolution {
rib bgp.l3vpn.0 {
resolution-ribs inet.0;
}
rib bgp.rtarget.0 {
resolution-ribs inet.0;
}
}
Thanks Adam for help!
Best regards,
Misak Khachatryan,
On Thu, Sep 13, 2018 at 1:28 PM Misak Khachatryan
mailto:m.
Well i think that also a problem of copy/pasting :)
Previously we had RR on a PE router and it seems i did simple copy/paste of
relevant config.
Can't remember any other reason to do that.
But Jason has a problem having only
set routing-options resolution rib bgp.l3vpn.0 resolution-ribs inet.0
.o issues with convergence or suboptimal paths. The noc is constantly
seeing high cpu alerts and that was concerning. Is this normal in other
networks?
Running 14.1R7.4 with mx480/240 mix.
I usually follow the code listed here:
https://kb.juniper.net/InfoCenter/index?page=content&id=KB21476
Whi
11 matches
Mail list logo
