> Of tim tiriche
> Sent: Wednesday, September 12, 2018 6:04 AM
>
> Hi,
>
> Attached is my MPLS Auto B/w Configuration and i see frequent path
> changes and cpu spikes. I have a small network and wanted to know if
there
> is any optimization/best practices i could follow to reduce the churn.
>
>
On 13/Sep/18 19:11, Saku Ytti wrote:
> New software is bad, old software is good adage is not data driven. We
> also need to understand what vendor is doing, how are they developing,
> how are they testing, how are they releasing and when they are
> changing something, in which release will the
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
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
.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
Hey Tim,
I'd optimise for customer experience, not CPU utilisation. Do you have
issues with convergence time, suboptimal paths?
Which JunOS you're running? There are quite good reasons to jump in
recent JunOS for RSVP, as you can get RSVP its own core, and you can
get make-before-break LSP reopti
Hi,
Attached is my MPLS Auto B/w Configuration and i see frequent path changes
and cpu spikes. I have a small network and wanted to know if there is any
optimization/best practices i could follow to reduce the churn.
protocols {
mpls {
statistics {
file mpls.statistics si
8 matches
Mail list logo