Key Name Description Impact Workaround Resolution
LM-7647 (WAF Insights) WAF Logs Missing Client IP address LoadMasters running firmware version 7.2.62 are affected by a bug that causes the Client IP to be missing from the Event logs. This impacts the Web Application Firewall (WAF) insights in LoadMaster 360, specifically the Top 10 and False Positives sections, where data will not be populated.

  • Incomplete WAF insights on LoadMaster 360

  • Missing client IP address in the LoadMaster logs

 You can downgrade the LoadMaster to a previous firmware version if WAF Insights is required. A fix is planned for a future LoadMaster firmware release.
LM-7791 (User Insights) L7 Request Logs Always Return a 200 Response Code On LoadMaster firmware version 7.2.62, the L7 Request Log returned from the LoadMaster always displays a 200 OK status, even when the actual response code is different. This can be misleading when displaying information under User Insights (specifically the Response code).

Inaccurate logging of HTTP response codes

 You can use LoadMaster firmware version 7.2.61 if accurate HTTP response codes are required. It is recommended to wait until a future LoadMaster firmware release. A fix is planned for a future LoadMaster firmware release.
AXXF-10721 Dashboards widgets are loading several times The Dashboards widgets for Application and LoadMaster Overview in the Overview Dashboard are loading several times when accessing the page. Multiple calls are being made to the backend. This will display a spinner multiple times until all the requests have been served. None currently available. This issue is under investigation. There is no confirmed fix or estimated fix time at present.
AXXF-13271 Error starting core services Deploying a Connector for the first time might result in an error starting core services This error is a timing error. LoadMaster 360 tries to check the health of the Connector. If there is any latency, this message will be displayed. It will normally display the correct status after a couple of minutes. We plan to resolve this bug as soon as possible.