thoffman at twitter.com
Wed Jun 1 12:35:57 EDT 2016
64bit RPD is newer, and by nature will have more bugs - so don't run this
unless you need it. Check this with "show task memory" - this will show
what you have used of the RPD accessible memory. As Phil notes, you'd need
significant RIB scale (which does exist in larger networks) to require
Enabling this will cause RPD to restart as you kill one process and start
On Wed, Jun 1, 2016 at 9:22 AM, Phil Rosenthal <pr at isprime.com> wrote:
> I’ll ask the obvious question — do you actually have a ‘need’ for this?
> Even on systems with many peers, 5+ full tables, and a full IGP mesh, I
> haven’t seen rpd much over 1GB of ram in use. 64bit rpd would only be
> beneficial if you have a need for a rpd process using more than 4GB of ram.
> Is this a theoretical use case, or is there an actual need?
> Best Regards,
> -Phil Rosenthal
> > On Jun 1, 2016, at 3:58 AM, Theo Voss <mail at theo-voss.de> wrote:
> > Hi,
> > has anybody enabled „system processes force-64bit“ on 64bit Junos? Have
> you done this during daily ops or during a maintenance window? According to
> Juniper documentation  rpd must not be restarted to enable 64-bit mode:
> „You need not restart the routing protocol process (rpd) to use the 64-bit
> > Thanks in advance for your comments! ;-)
> > Cheers,
> > Theo Voss
> > _______________________________________________
> > 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
Tim Hoffman | Twitter, Inc.
1355 Market St. | San Francisco, CA | 94103
More information about the juniper-nsp