Deployment Architecture

Upgrade Splunk Deployment

malopez_riv
Engager

Hi!

I´m looking for your help because I want to upgrade my Splunk deployment. Currently, I have all my forwarders running with the 6.2.3 version (my forwarders are running FreeBSD OS), my indexer and search head are running the 7.3 version (Those devices running in CentOS 11.2). The big question here,  can I update my indexer and search head device to the 8.1.0.1 and mantain my forwarders in the 6.2.3 version? will the forwarders send events to the indexer without problem?

I'm considering two scenarios for my upgrade:

Forwarders in version 6.2.3 -> Indexer in version 8.1.0.1 -> Search Head in version 8.1.0.1

or

Forwarders in version 6.2.3 -> Indexer in version 7.2.3 -> Search Head in version 8.1.0.1

 

What do you think guys?

 

I really appreciate any help that you can bring me!!

Labels (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Can't do it.  Splunk 8.x doesn't support forwarders that old.  See https://docs.splunk.com/Documentation/VersionCompatibility/current/Matrix/Compatibilitybetweenforwar...

You could keep the old indexers, but the 8.x search heads won't be able to take advantage of all of the new 8.x features.  

---
If this reply helps you, Karma would be appreciated.
0 Karma
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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...