Note: Utilizing WAF can have a significant performance impact on the LoadMaster deployment. Please ensure that the appropriate resources are allocated.

For virtual and bare metal LoadMaster instances, a minimum of 2GB of allocated RAM is required for the operation of WAF. The default memory allocation for Virtual LoadMasters and LoadMaster Bare Metal instances before LoadMaster Operating System version 7.1-22 is 1 GB of RAM. If this default allocation has not been changed, modify the memory settings before proceeding with the WAF configuration. If the check box to enable WAF is grayed out, it could mean that the LoadMaster does not have enough memory to run WAF.

There is a WAF engine open connection limit of 64000 per Virtual Service.

Note: To reduce the risk of the WAF connection limit being reached, the open connections will be closed after 20 seconds when a remote log server is too slow to respond. There is no impact on connections in use.
CAUTION: Legacy WAF (WAF Options (Legacy)) was fully deprecated as part of the v7.2.61 release. Deprecated means that Progress Kemp fully removed WAF Options (Legacy) from the LoadMaster. If you are running WAF Options (Legacy) and upgrade to the v7.2.61 release, a warning will be provided and the new WAF engine will be enabled with default values. We recommend updating your LoadMaster to use the latest WAF feature prior to upgrading to 7.2.61 so that you can configure the WAF engine to suit your configuration at the earliest possible convenience. For more details, refer to the following section: Converting from Legacy WAF to OWASP WAF of WAF Feature description document.