topic Re: CoreXL disabled by default on AWS Cloudguard (r80.20) in General Topics

CoreXL disabled by default on AWS Cloudguard (r80.20)

Jose_Rivera — Sat, 07 Dec 2019 07:02:04 GMT

Just noticed CoreXL is disabled on all the CloudGuard instances we deployed (based on R80.20, soon to be R80.30).

We do have a ton of route based tunnels configured and want to make sure we are leveraging multi-core VPN.

Doesn't multi-core VPN require CoreXL? Is it supported to enable CoreXL on these AWS CloudGuard instances?

We have 8 core instances and no blades other than VPN and Identity Awareness enabled at the moment.

Thanks.

Re: CoreXL disabled by default on AWS Cloudguard (r80.20)

PhoneBoy — Sat, 07 Dec 2019 16:46:35 GMT

Unless you're using less than 4 cores, I can't think of a reason CoreXL should be disabled on any appliance (real or virtual).
You should be able to enable it via cpconfig, though it raises the question why it is necessary.

Re: CoreXL disabled by default on AWS Cloudguard (r80.20)

HeikoAnkenbrand — Sat, 07 Dec 2019 16:58:47 GMT

With 8 cores, normally 2 SND instances and 6 CoreXL instances should be enabled by default. If this is not the case, I would configure it using cpconfig.

Re: CoreXL disabled by default on AWS Cloudguard (r80.20)

Jose_Rivera — Mon, 09 Dec 2019 15:47:20 GMT

Thanks for the replies. We will enable CoreXL and monitor the Gateways.

Can someone still let me know if multi-core VPN requires CoreXL be enabled?

Re: CoreXL disabled by default on AWS Cloudguard (r80.20)

PhoneBoy — Mon, 09 Dec 2019 16:43:43 GMT

Any feature leveraging multiple cores requires CoreXL to be enabled.