[j-nsp] debug messages - kernel: rt->rt_proto and fpc0 Next-hop resolution requests throttled

Hello friends, Curiosity may have killed the cat, but I'm not a cat so here goes. Evaluating some debug logs on an EX-9208 I've seen two flavors of log messages that I'd be interested in learning more about. One set looks like the following: /kernel: rt->rt_proto ipv4 plen 32 /kernel:

Re: [j-nsp] Fate sharing between BGP and RSVP

See also: http://www.juniper.net/documentation/en_US/junos15.1/topics/usage-guidelines/mpls-configuring-traffic-engineering-for-lsps.html On Wed, Sep 14, 2016 at 09:20:17AM +0200, Dragan Jovicic wrote: > So you want BGP to resolve routes using only inet.3 table which contains > RSVP routes, and

Re: [j-nsp] Fate sharing between BGP and RSVP

If you make your LSP with a strict path where it will not use the other IGP path then you can use a forwarding table export policy to force the LSP as a strict next next hop: policy-statement name-of-policy { term term-1 { from ; then { install-nexthop strict lsp

Re: [j-nsp] DCU matching in firewall filter

DCU on FT is executed on ingress PFE after routing decision. This means you can attach it to inet family regardless of egress encapsulation (MPLS). Junos 14.X did not allow me to configure interface-groups and FT egress filter. But interface sets seem to be good enough for this. Dragan On Tue,

Re: [j-nsp] Fate sharing between BGP and RSVP

So you want BGP to resolve routes using only inet.3 table which contains RSVP routes, and not inet.0. https://www.juniper.net/documentation/en_US/junos15.1/topics/example/vpns-layer-3-route-resolution-route-reflector.html Dragan On Wed, Sep 14, 2016 at 1:26 AM, Rob Foehl