Closed gregcoward closed 1 year ago
I have the same problem after recent upgrade to Big IP 16.1.3.2.
I've been in contact with F5 support. In my case, the issue was caused by a new db key which by default prohibits loopback addresses in irules.
If you have configured a local listener, with an irule such as "when CLIENT_ACCEPTED {\n node 127.0.0.1 6514\n}"
then you need to run the following tmsh command. modify sys db tmm.tcl.rule.node.allow_loopback_addresses value true
Hi, F5 BIG-IP Telemetry Streaming is entering a phase of ongoing maintenance and support. A product in maintenance mode continues to receive support and ensures its stability with regular critical fixes and security updates. This maintenance approach helps maintain the longevity and reliability of the product for the long term. Enhancement requests for this product will be evaluated on an individual basis, taking into consideration their overall impact and alignment with our business objectives. Only those with a strong case for improvement will be considered for implementation. There is no plan to deprecate this product. If you have a business case for this, please let me know and I will let you know how to contact us. Thank you
Environment
Summary
The appears to be an issue with the TS listener and the BIG-IP. After upgrading to the above noted version, telemetry events are no longer being generated for events, (AVR, LTM, ASM, AFM). System poller event collection is functioning correctly. This issue has been noted in three separate environments utilizing a combination of Splunk and generic consumers.
This has been reproduced using the following versions utilizing the same device and identical configurations:
Steps To Reproduce
Steps to reproduce the behavior: