topic Re: kernel instances running on unlicensed cores in Firewall and Security Management

kernel instances running on unlicensed cores

tomjoos — Wed, 01 Apr 2020 02:49:29 GMT

We are licenced for 2 cores in an open server. ctl affinity shows that the kernel instances are running on unlicensed cores. Will that impact the performance of the security gateway? Is the recommended method the interfaces and kernel instances use only the licenced cores?

CPU 0:
CPU 1: eth1
CPU 2:
CPU 3: eth2
CPU 4: eth5
CPU 5: eth4
CPU 6: eth6
CPU 7: eth0
CPU 8: eth2
CPU 9: fw_1
CPU 10: eth4
CPU 11: fw_0
All: vpnd mpdaemon fwd cprid cpd
The current license permits the use of CPUs 0, 1 only.

Re: kernel instances running on unlicensed cores

PhoneBoy — Wed, 01 Apr 2020 05:05:59 GMT

What version/JHF level is this?
The fact the gateway is even allowing those unlicensed cores to be used is definitely a bug and it definitely could cause some issues.
Can you give the output of cplic print with sensitive data masked?

Re: kernel instances running on unlicensed cores

tomjoos — Wed, 01 Apr 2020 05:24:15 GMT

ver 77.30 jumbo Hf_ Take 292

Licence info follows

cpsg-c-2-500-ha cpsb-fw-ha cpsg-u cpsb-vpn-ha cpsb-ia-ha

Re: kernel instances running on unlicensed cores

HeikoAnkenbrand — Wed, 01 Apr 2020 05:39:03 GMT

Was the system operated with a trail license or with an eval lizeznz and not rebooted afterwards?

The trail license is by default 15 days active after installation.

Re: kernel instances running on unlicensed cores

HeikoAnkenbrand — Wed, 01 Apr 2020 05:41:23 GMT

Note: R77.30 is no longer supported.

Re: kernel instances running on unlicensed cores

Timothy_Hall — Wed, 01 Apr 2020 13:18:09 GMT

This, the 2-core license has been applied but the system was loaded/booted up under the Trial License or a 30-day eval. Be sure to set number of CoreXL instances to 2 with cpconfig prior to rebooting to avoid the Trial License "Core Crunch" as described in my book.