[j-nsp] R: Routing Instance BGP Full Routing High Memory persists

[Diogo Montagner]

A good document that explains how the memory allocation works:

http://www.juniper.net/techpubs/en_US/junos/information-products/topic-collections/nce/rpd-memory-faq/rpd-memory-faq.pdf

Thanks

./diogo -montagner
JNCIE-SP 0x41A


On Sun, Dec 2, 2012 at 3:18 AM, Giuliano Medalha <giuliano at wztech.com.br>wrote:

> Maybe if we restart the RPD process for master instance it could free
> memory ?
>
>
>
>
> WZTECH is registered trademark of WZTECH NETWORKS.
> Copyright © 2012 WZTECH NETWORKS. All Rights Reserved.
>
> The information transmitted in this email message and any attachments are
> solely for the intended recipient and may contain confidential or
> privileged information. If you are not the intended recipient, any review,
> transmission,  dissemination or other use of this information is
> prohibited. If you have received this communication in error, please notify
> the sender immediately and delete the material from any computer, including
> any copies.
>
>
>
> On Sat, Dec 1, 2012 at 2:08 PM, Yannick LE TEIGNER <
> yannick.leteigner at gmail.com> wrote:
>
> > Memory allocation is complex topic. The memory may have been released by
> > RPD but the kernel still keeps it allocated for RPD - really releasing it
> > only if another process needs it.
> > One way to check would be to create a dummy shell script to consume a
> > large part of memory and then kill it. It would then be interesting to
> see
> > if your 'show chassing routing-engine' shows the same output.
> >
> >
> >
> > On Sat, Dec 1, 2012 at 9:09 AM, Riccardo S <dim0sal at hotmail.com> wrote:
> >
> >> With m7 the only useful action solving the issue was reboot...
> >>
> >> sent with Android
> >>
> >> Giuliano Medalha <giuliano at wztech.com.br> ha scritto:
> >>
> >> >People,
> >> >
> >> >We are doing some BGP tests using routing-instances on MX5-T-DC
> routers.
> >> >
> >> >We have created a routing-instance to receive 3 full routing inet.0
> >> tables.
> >> >
> >> >The master routing has 3 majors full routing tables too.
> >> >
> >> >Before the tests we check the RE percentage of using memory ... using:
> >> >
> >> >Router> show chassis routing engine
> >> >
> >> >It show 47% usage.
> >> >
> >> >After the creation of the routing-instance (type virtual-router) -
> named
> >> >TEST  we could receive more 3 full routing tables on the TEST.inet.0
> >> table
> >> >
> >> >Using the same command is show to us:
> >> >
> >> >Router> show chassis routing engine
> >> >
> >> >87% memory utilization
> >> >
> >> >After we remove the routing-instance configuration with a commit
> command
> >> in
> >> >sequence ... it still shows the same 87% of memory utilization
> >> >
> >> >It this procedure is correct ?    Is it any update command to clear the
> >> >memory allocation without disrupting forwarding services ?
> >> >
> >> >Can you please give me some feedback about it ?
> >> >
> >> >Did anyone see it before ?
> >> >
> >> >Thanks a lot,
> >> >
> >> >Giuliano
> >> >_______________________________________________
> >> >juniper-nsp mailing list juniper-nsp at puck.nether.net
> >> >https://puck.nether.net/mailman/listinfo/juniper-nsp
> >> >
> >>
> >> _______________________________________________
> >> juniper-nsp mailing list juniper-nsp at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>
> >
> >
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>