- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Re: CPU Affinity Problem
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CPU Affinity Problem
Hello mates,
I've running with some problems with my security gateway.
It's a robust 16000 model with forty-eight cores.
Every week i need to check the affinity of CPUs for the vpnd and pdpd process, because on extreme days (more than seven hundred vpn connections) if the vpnd and pdpd is set to one core only, crashes the process and all my tunnels goes down.
PS: The auto (for some reason) defined core runs over 95% all the time unless I set more CPU cores to the process.
So, I set a suitable number of cores and runs fine for some days. Is there some automatic routine that changes this? Because every week the change comes back to only one core, and I need to monitor if everything is set properly.
Any advice?
Regards,
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The SK looks like it applies to R80.40 precisely because that's where the bug was found.
There's nothing that suggests this bug doesn't exist in other releases as well.
Regardless, a TAC case is needed to get to the bottom of it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
vpnd is a child process of fwd, and this appears to be a known issue: sk173931: Wrong affinity for FWD child processes
March 27th with sessions for both the EMEA and Americas time zones
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Timothy_Hall ,
Thanks for your reply.
I didn't mention it before, but we are running r80.30 yet.
Planning to upgrade the the next two months.
The SK is valid only for 80.40?
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not sure, but it probably applies to R80.30 as well; you'll need to open a TAC case to find out. @PhoneBoy can you ask/alert the owner of the SK?
March 27th with sessions for both the EMEA and Americas time zones
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The SK looks like it applies to R80.40 precisely because that's where the bug was found.
There's nothing that suggests this bug doesn't exist in other releases as well.
Regardless, a TAC case is needed to get to the bottom of it.
