|
|
|
CoreXL creates multiple firewall instances that are, in reality, independent firewalls. You can use CoreXL to increase the performance of the VSX Gateway on an open server or appliance with multiple cores. You can also assign each instance to a group of CPU cores with the fw ctl affinity command.
You configure firewall instances differently for the VSX Gateway (VS0) than for other Virtual Systems.
You can configure multiple instances for each Virtual System. When you change the number of firewall instances on a Virtual System, there is some downtime for that Virtual System.
|
Important - Each firewall instance that you create uses additional system memory. A Virtual System with five instances would use approximately the same amount of memory as five separate Virtual Systems. |
The number of IPv6 instances cannot exceed the number of IPv4 instances. For more about IPv6 instances and VSX, go to sk97997.
For more about configuring CoreXL, see the R80.30SP Maestro Performance Tuning Guide - Chapter CoreXL.
Use the "g_all cp_conf corexl" command to configure the CoreXL on Security Group members. The number of CoreXL Firewall instances for the VSX Gateway is limited to the physical number of CPU cores on the Security Group members.
Note - If you run this command in a Virtual System, the output applies to VS0.
Use SmartConsole to configure the number of CoreXL Firewall instances on the Virtual Systems.
The number of CoreXL Firewall instances is not limited by the physical CPU cores on the VSX Gateway.
You can assign the number of IPv6 CoreXL Firewall instances. It must be less or equal to the number of IPv4 CoreXL Firewall instances. The number of IPv6 CoreXL Firewall instances may be zero. IPv6 CoreXL Firewall instances are only enabled, if an IPv6 address is configured for that Virtual System.
Notes:
To configure CoreXL on a Virtual System:
The Virtual System General Properties window opens.
