[j-nsp] Stealing from MX firewall jtree space

[Krasimir Avramski]

Hello,

route-memory-enhanced introduced in 9.6

What about terminating bgp neighbor in inet.0 with bgp operating over a
rib-group under family inet:

protocols bgp
group xy {
    neighbor x.x.x.x {
        import xy;
        family inet {
            unicast {
                rib-group xy;
            }
        }
    }
}

Then import routing-policy "xy" states:

policy-statement xy
term 1 {
    from community to_inet_0;
    to rib inet.0;
    then accept;
}
term 2 {
    to rib inet.0;
    then reject;
}
term 3 {
    from community to_vrf;
    to rib vrf.inet.0;
    then accept;
}
term 4 {
    to rib vrf.inet.0;
    then reject;
}


Best Regards,
Krasi

On Wed, Dec 16, 2009 at 10:25 PM, Richard A Steenbergen <ras at e-gerbil.net>wrote:

> On Wed, Dec 16, 2009 at 11:54:33AM -0800, Derick Winkworth wrote:
> > ##########
> > To allocate more memory for routing tables, include the
> route-memory-enhanced
> > statement at the [edit chassis] hierarchy level:
> > [edit chassis]
> > route-memory-enhanced;
> > ##########
> >
> > You have to restart the FPC once you do this...
>
> What code is that in? No love in 9.5.
>
> --
> Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>