Last Modified: Feb 11, 2025
Affected Product(s):
BIG_IP_NEXT(CM) TMOS
Known Affected Versions:
20.2.0, 20.2.1
Fixed In:
20.3.0
Opened: May 16, 2024 Severity: 1-Blocking Related Article:
K000140380
When you go to Instance > Log Management in BIG-IP Next Central Manager and set up an external logger, the Central Manager will no longer receive any telemetry while the configured external logger will get all of the available logs from the BIG-IP Next instance. When new external loggers are configured, only the last will receive any telemetry, while all previously configured external loggers will stop receiving telemetry.
Configured Central Manager stops receiving telemetry. Other external loggers stop receiving telemetry too.
Configure external logger for the BIG-IP Next instance.
F5 offers two bash scripts that you can run via the Central Manager CLI, one to identify impacted instances (find_broken_telemetry_instances.sh) and a second script to fix telemetry streaming to Central Manager (update_cm_logger.sh). There is no workaround for allowing streaming telemetry to Central Manager and external loggers without the fix.
The creation or deletion of external loggers no longer interferes with other loggers, including telemetry. Although the certificates for the external loggers are visible in the “Certificates & Keys” screen, they cannot be deleted or updated from there.