Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Jose_Rivera
Participant

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

Jump to solution

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.

0 Kudos
Reply
1 Solution

Accepted Solutions
HeikoAnkenbrand
Champion
Champion

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.

View solution in original post

4 Replies
PhoneBoy
Admin
Admin
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.
HeikoAnkenbrand
Champion
Champion

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.

View solution in original post

Jose_Rivera
Participant

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?

0 Kudos
Reply
PhoneBoy
Admin
Admin
Any feature leveraging multiple cores requires CoreXL to be enabled.
0 Kudos
Reply