Hi, any expert help on this topic would be much appreciated.
Historically we run VSX with ClusterXL and Dynamic balancing disabled. Distribution of VSX VS's is equally loaded as well as manually set for some environments. This was rolled out before my time so not sure if this is the recommended config or the reason for those historic choices.
I have read the SK's on ClusterXL and Dynamic balancing VSX section but still don’t fully understand what the recommended ClusterXL and Dynamic balancing configuration would be for a load sharing VSX Cluster.
I am looking to build a new VSX cluster with 3 x 16200 running R81.10 latest JHF for a new project. My thoughts are we should enable ClusterXL as well as Dynamic balancing and enable VS load sharing just in case we get hit with Elephant Flows on the public VS's which did cause us significant performance issues in the past.
Expert advice on the above scenario and clarification on recommended CP config would be much appreciated.
I have checked VSX R81 Admin guide "Optimising VSX" section and there is very little in there.
Thanks for your help.
Our existing Historic VSX config
ClusterXL and Dynamic balancing is disabled.
Distribution of VSX VS's is equally loaded.
VS Load Sharing - Menu
1. Display current VS Load sharing configuration
2. Distribute all Virtual Systems so that each cluster member is equally loaded
I read the SK below but I still dont know if those are recommended options.
Dynamic Balancing for CoreXL- sk164155
How does it work with VSX?
Dynamic Balancing in VSX is similar to Security Gateways in that it aims to balance the SNDs and FWs cores. As opposed to Security Gateways, FW instances do not have static core affinity, and their amount does not determine the amount of SNDs. As a result, Dynamic Balancing does not require a certain amount of FW instances to be configured, and only adjusts their core affinity.
When adding an SND, the feature sets the affinity of FWK processes in all VSs to the list of new cores (rather than move a FW instance from one core to a different core, as done in Security Gateways). The maximum quantity of SND cores will be according to the NIC driver, with the highest number of queues in all VSs.
When you add a VS, the feature sets the new VS’s FWK to the current FWKs cores affinity.
If Dynamic Balancing is enabled, is CoreXL setting in cpconfig disabled ? Meaning I am not able to change CoreXL numbers?
No, but changes made in the CoreXL cpconfig only take effect after reboot. Note that rebooting with a non-default instance number (i.e. manual changes done by the user) will prevent Dynamic Balancing from starting in order not to overwrite users' actions (a proper alert to the user is to be sent in such cases).