Scenario |
Explanation and next steps |
---|---|
After reboot, the wrong interfaces are configured for Multi-Queue. |
This can happen after changing the physical interfaces on the Security Gateway. Follow one of these steps:
|
After you configure the Multi-Queue and reboot the Security Gateway, some of the configured interfaces show as These interfaces were up before the Security Gateway reboot. The |
This can happen when not enough IRQs are available on the Security Gateway. Follow one of these steps:
|
When you change the status of interfaces, all the interface IRQs are assigned to CPU 0, or to all of the CPU cores. |
This can happen when an interface status is changed to UP after the automatic affinity procedure runs (during each boot). Run:
This problem does not occur if SecureXL Affinity is set to Automatic mode ( |
In VSX mode, an fwk process runs on the same CPU core as some of the interface queues. |
This can happen when the affinity of the Virtual System was manually changed but Multi-Queue was not reconfigured accordingly. Follow one of these steps:
|
In Gateway mode, after you change the number of CoreXL Firewall instances, the Multi-Queue is disabled on all interfaces. |
When you change the number of CoreXL Firewall instances, the number of active RX queues automatically changes based on this formula (if it is not configured manually): Active RX queues = (Number of CPU cores) - (Number of CoreXL Firewall instances) If the difference between the number of CPU cores and the number of CoreXL Firewall instances is 1, Multi-Queue is disabled. Configure the number of active RX queues manually with this command:
|