Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
zarkathus
Participant
Jump to solution

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,

0 Kudos
1 Solution

Accepted Solutions
PhoneBoy
Admin
Admin

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.

View solution in original post

5 Replies
zarkathus
Participant
 

cpu_aff.png

0 Kudos
Timothy_Hall
Legend Legend
Legend

vpnd is a child process of fwd, and this appears to be a known issue: sk173931: Wrong affinity for FWD child processes

Gateway Performance Optimization R81.20 Course
now available at maxpowerfirewalls.com
0 Kudos
zarkathus
Participant

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, 

0 Kudos
Timothy_Hall
Legend Legend
Legend

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?

Gateway Performance Optimization R81.20 Course
now available at maxpowerfirewalls.com
PhoneBoy
Admin
Admin

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.

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events