[j-nsp] force-64bit

[Theo Voss]

I’ve lost a rpd suddenly during daily ops a couple of month ago by OOM, ATAC investigated the issue for months and conclusion was solely OOM. Referring to my question, Tim says "Enabling this will cause RPD to restart as you kill one process and start another.“. That’s what I suspected, but is contradictory to the Juniper documentation, thanks! :-)



Best,
Theo

-----Ursprüngliche Nachricht-----
Von: Phil Rosenthal <pr at isprime.com>
Datum: Mittwoch, 1. Juni 2016 um 18:22
An: Theo Voss <mail at theo-voss.de>
Cc: "juniper-nsp at puck.nether.net" <juniper-nsp at puck.nether.net>
Betreff: Re: [j-nsp] force-64bit

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 [1] rpd must not be restarted to enable 64-bit mode: „You need not restart the routing protocol process (rpd) to use the 64-bit mode.“...
> 
> Thanks in advance for your comments! ;-)
> 
> https://www.juniper.net/documentation/en_US/junos14.2/topics/reference/configuration-statement/routing-edit-system-processes.html
> 
> 
> Cheers,
> Theo Voss
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp