Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- Having to restart heavy forwarder to get data from...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Having to restart heavy forwarder to get data from F5 network devices through control API
I have configured f5 network devices to a Heavy Forwarder. The data gets ingested for some time and then again it stops getting indexed. Every time I have to restart Splunk services on HF to start the indexing for F5 devices.
I got below error through internal logs on HF :
2019-06-19 14:53:17,812 ERROR pid=97727 tid=Thread-4677 file=F5_iControl_API.py:run:92 | Exception (it may be caused by unreachable F5 server "ip address" or wrong iControl API "Management.Folder.get_traffic_group" in configured template): Server raised fault: 'Exception caught in Management::urn:iControl:Management/Folder::get_traffic_group()
There are many errors like this.
Can someone please help me?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What Splunk Version and App are you using?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk HF is 7.0.1 , For app I don't know how to check but if I check in apps.conf it is: 2.6.0(for f5 app)
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This exception indicates a connectivity issue to your F5
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is it a fault from Splunk side or something with F5 devices itself? What can be done in such situations? How to resolve this issue?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Does anyone know about this, I am stuck not able to use this addon due to this issue
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass
May 2026 Splunk Expert Sessions: Security & Observability
Network to App: Observability Unlocked [May & June Series]
