Last Modified: Feb 11, 2025
Affected Product(s):
BIG_IP_NEXT(CM) TMOS
Known Affected Versions:
20.2.0, 20.2.1
Opened: Apr 17, 2024 Severity: 2-Critical
BIG-IP Next Instance telemetry can be missing from the BIG-IP Next Central Manager for five to ten minutes if any of the BIG-IP Next Central Manager HA nodes go down or unavailable. - Instance data metrics such as Instance health, Traffic, and Network Interface metrics will be lost, as they are available only for the previous hour. - All other data such as Application metrics and WAF logs, will not be lost. However, these metrics could be unavailable for 5-10 minutes during the node down event.
BIG-IP Next instance data metrics, such as instance health, traffic, and network interface metrics, will be lost. All other metrics, such as application metrics and WAF logs, might be missing for 5-10 minutes.
Any of the nodes in the BIG-IP Next Central Manager HA Nodes becomes unavailable or goes down.
Wait for 5-10 minutes and BIG-IP Next Telemetry data will resume on the BIG-IP Next Central Manager. Run the following command on the VM console of the BIG-IP Next Central Manager to resume the instance data metrics: kubectl delete pods prometheus-mbiq-kube-prometheus-prometheus-0 --grace-period=0 --force
None