When troubleshooting a performance problem on multicore firewall that is using CoreXL, what command checks the number of connections each core is processing?
A. fw ctl multik stat
B. fw CTL pstat
C. sim affinity -l
D. cat fwkern.conf
One Comment on “what command checks the number of connections each core is processing?”
Sidzasays:
fw ctl multik stat
Background:
Displays status of CoreXL instances and summary for traffic that passes through each CoreXL FW instance (current number and peak number of concurrent connections)
Diagnostics:
Collect this output to see the current status
Analysis:
Check the number and the allocation of FW instances to CPU cores (in cluster, the output must be identical on all members)
Check the peak number connections on FW instances (instances should be loaded as equally as possible)
Example from machine with 4 CPU cores (1 SND + 3 CoreXL FW instances):
fw ctl multik stat
Background:
Displays status of CoreXL instances and summary for traffic that passes through each CoreXL FW instance (current number and peak number of concurrent connections)
Diagnostics:
Collect this output to see the current status
Analysis:
Check the number and the allocation of FW instances to CPU cores (in cluster, the output must be identical on all members)
Check the peak number connections on FW instances (instances should be loaded as equally as possible)
Example from machine with 4 CPU cores (1 SND + 3 CoreXL FW instances):
ID | Active | CPU | Connections | Peak
———————————————-
0 | Yes | 3 | 26 | 66
1 | Yes | 2 | 36 | 64
2 | Yes | 1 | 39 | 53
1
0