The information you are about to copy is INTERNAL!
DO NOT share it with anyone outside Check Point.
All interfaces are affined to CPU0 after upgrading Security Gateway with enabled CoreXL on machine with 2 CPU cores to R77.30
Gaia, SecurePlatform 2.6
Platform / Model
After upgrading a Security Gateway with enabled CoreXL on machine with 2 CPU cores (i.e., each CPU runs a CoreXL FW instance and as SND) to R77.30, only CPU0 is handling IRQs, and CPU1 is not handling any IRQs - all interfaces are affined only to CPU0 (i.e., each CPU runs a CoreXL FW instance, but only one CPU runs as SND).
Output of "sim affinity -l" command always shows that affinity of all interfaces it set to CPU 0:
eth0 : 0
eth1 : 0
eth2 : 0
eth3 : 0 etc.
Output of "fw ctl affinity -l -a -v" command always shows that affinity of all interfaces it set to CPU 0.
Interface eth0 (irq 139): CPU 0
Interface eth1 (irq 234): CPU 0
Interface eth2 (irq 107): CPU 0
Interface eth3 (irq 75): CPU 0
Kernel fw_0: CPU 1
Kernel fw_1: CPU 0
Daemon in.geod: CPU all
Daemon mpdaemon: CPU all
Daemon rtmd: CPU all
Daemon fwd: CPU all
Daemon cpd: CPU all
Daemon cprid: CPU all
Configuring manual SIM Affinity with "sim affinity -s" command resolves the issue.
Configuring automatic SIM Affinity with "sim affinity -a" command after configuring manual SIM Affinity, causes the above issue to reoccur.
Issue is caused due to changes in the return values of fwaffinity_used_cpus script on machines where the number of CoreXL FW instances equals the number of total CPU cores (as in 2 cores machines).