Deployment Architecture

How do I configure a small installation?

danielbb
Motivator

I have an indexer, a search head, and a heavy forwarder for a small installation. How do I configure them to communicate correctly?

Labels (1)
Tags (1)
0 Karma

kiran_panchavat
SplunkTrust
SplunkTrust

@danielbb Please, don't forget to accept this solution if it fits your needs. 

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!

isoutamo
SplunkTrust
SplunkTrust
If this a production or anything else than your lab environment, then you should configure TLS into use on those connections. There are instructions on securing your splunk environment guide and also there is conf23 presentation about TLS slippery or something similar.
0 Karma

kiran_panchavat
SplunkTrust
SplunkTrust

@danielbb 

kiran_panchavat_0-1736788809973.png

I hope this helps, if any reply helps you, you could add your upvote/karma points to that reply, thanks.

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!

kiran_panchavat
SplunkTrust
SplunkTrust

@danielbb 

Create `inputs.conf` and `outputs.conf` on the Heavy Forwarder (HF) if you want to forward data directly from the HF to the indexers. Alternatively, create `inputs.conf` and `outputs.conf` on the Universal Forwarder (UF) to send data to the HF, which will then forward it to the indexers.

I hope this helps, if any reply helps you, you could add your upvote/karma points to that reply, thanks.

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!

kiran_panchavat
SplunkTrust
SplunkTrust

@danielbb Hello Daniel, Please follow the below steps.

1. Install Splunk on all the required instances.

2. Enable the receiving port `9997` on the indexer.

3. If you are forwarding data from a Universal Forwarder (UF) to a Heavy Forwarder (HF) and then to the indexer, ensure the receiving port is open on both the Heavy Forwarder and the indexer.

4. Ensure the following ports are open:

9997: UF to HF and HF to Indexer

8089: Management port between Indexers and Search Heads

8000: Web port for HF and Search Head (optional for indexers in production environments)

5. Add your indexer to the Search Head:

- Navigate to Settings > Distributed Search > Distributed Search Setup

- Enable distributed search, then go to Settings > Distributed Search > Search Peers

- Add the indexer details here and restart the Splunk instance.

6. If required, open port `8000` for the web interface on the Heavy Forwarder and Search Head. While optional for indexers, this port is typically not opened on production indexers.

Note:Before configuring Splunk, perform a telnet test to verify port connectivity:

- From UF to HF:

`telnet <HF_IP_Address> 9997`

- From HF to Indexer:

`telnet <Indexer_IP_Address> 9997`

- From Indexers to Search Heads:

Ensure the management port `8089` is open.

I hope this helps, if any reply helps you, you could add your upvote/karma points to that reply, thanks.

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...