SNMPv3 traps may fail to be processed by certain third-party monitoring tools (such as Zabbix) due to a lack of support for EngineID discovery through the snmpFrameworkMIB OID. Despite the EngineID being included in the trap packet, some monitoring tools require this specific OID for SNMPv3 trap synchronization.

HTTP health checks using HTTP CONNECT (with Local CONNECT or Remote CONNECT) intermittently stopped functioning and caused elevated CPU utilization. This resulted from a data size mismatch between expected and received health check responses, which caused the health check process to hang and required a manual process restart to restore monitoring and traffic flow.

Layer 7 TCP virtual servers using the PERSIS_HASH_SRC_ADDR persistence method experienced a rapid memory leak, leading to service instability and high memory utilization. This resulted from a failure to release memory during frequent virtual server configuration updates, which were triggered by unstable health check statuses.