Splunk® Supported Add-ons

Splunk Add-on for F5 BIG-IP

Download manual as PDF

Download topic as PDF

Hardware and software requirements for the Splunk Add-on for F5 BIG-IP

Prerequisites

You need to know the credentials for the F5 BIG-IP servers from which you want to collect data. The F5 BIG-IP user that is used to collect data with this add-on needs to be created in the Common partition and have permission to access all other partitions from which you want to collect data. Also, only one F5 BIG-IP user can be used to collect data from a single F5 BIG-IP server. In other words, multiple user accounts cannot be used to collect data from any one F5 BIG-IP server.

F5 BIG-IP modules

This add-on supports version 10.1.0 - 12.0.0 of the BIG-IP system software modules.

  • BIG-IP Local Traffic Manager (LTM)
  • BIG-IP DNS (known as Global Traffic Manager (GTM) in versions prior to 12.0.0)
  • BIG-IP Access Policy Manager (APM)
  • BIG-IP Application Security Manager (ASM)

Splunk platform requirements

Because this add-on runs on the Splunk platform, all of the system requirements apply for the Splunk software that you use to run this add-on.

  • For Splunk Enterprise system requirements: see System Requirements in the Splunk Enterprise Installation Manual.
  • For Splunk Light system requirements: see System Requirements in the Splunk Light Installation Manual.
  • If you are managing on-premises forwarders to get data into Splunk Cloud, see System Requirements in the Splunk Enterprise Installation Manual, which includes information about forwarders.

Sizing requirements for the Splunk Add-on for F5 BIG-IP

These sizing requirements are for a single Splunk platform instance running the Splunk Add-on for F5 BIG-IP and collecting iControl data via modular inputs. There are no specific sizing requirements if you are only collecting data over syslog.

The requirements specified ensure that the Splunk platform can collect data from your F5 BIG-IP servers without disruption in data flow.

Memory allocation requirements for Templates.

  • 200M± if you do not use the pre-defined templates.
  • 400M± if you use all of the templates.
  • 150M± for the LocalLB template.
  • 130M± for the GlobalLB template.
  • 50M± for the System template.
  • 70M± for the Networking template.
  • 70M± for the Management template.

CPU requirements.

  • 8 CPUs, 1 Core per CPU, CPU MHz 2699.591

Recommended configurations for optimal data collection

If you are collecting iControl API data via SOAP, Splunk recommends the following configurations for optimal data collection performance.

  • A single Splunk platform instance monitors no more than three F5 BIG-IP servers concurrently.
  • A task monitors no more than two F5 BIG-IP servers at a time.
  • Assign no more than one task to an F5 BIG-IP server.

If you are collecting iRules and other syslog data, a single heavy forwarder can collect data from twenty or more F5 BIG-IP devices.

PREVIOUS
Installation overview for the Splunk Add-on for F5 BIG-IP
  NEXT
Installation overview for the Splunk Add-on for F5 BIG-IP

This documentation applies to the following versions of Splunk® Supported Add-ons: released


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters