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 R77 Performance Tuning Administration Guide.
Included Topics |
Use the cpconfig
command to configure CoreXL on the VSX Gateway (VS0). The number of instances for the VSX Gateway is limited to the physical number of cores on the server or appliance.
To configure the number of instances on the VSX Gateway:
cpconfig
.cpconfig
.Note - It is not necessary to reboot the VSX Gateway after you configure CoreXL. |
Use SmartDashboard to configure the number of firewall instances on the Virtual Systems. You can assign up to 10 instances on a Virtual System. The number of instances is not limited by the physical cores on the VSX Gateway server or appliance.
We recommend that you use the number of instances for each Virtual System according to the expected network traffic on the Virtual System. Configuring unnecessary instances will have an impact on performance.
We recommend that you do not configure more instances than the total number of physical cores on the VSX Gateway server or appliance.
To configure CoreXL on a Virtual System:
The Virtual System General Properties window opens.