Hello everyone, could you help me.
I have a splunk Heavy Forwarder server, version 8.1.14, it simply forwards data from a closed zone of our network.
I need to update it to version 9.4.
Judging by the splunk documentation, this is possible if I understood everything correctly.
I would like to make a test stand, but I can’t find the splunk 8.1.14 version in Previous Releases of Splunk Enterprise.
Maybe someone has a download link?
Hi @igor5212
TL;DR: upgrade path should be 8.1.14 -> 9.0.9 -> 9.2.8 -> 9.4.x
The advice from @thahir here is not correct so please be careful ("upgrading from Splunk 8.1.14 to 9.4 is supported, as Splunk supports direct upgrades between any two minor/patch versions") - This is not the case. Please see https://docs.splunk.com/Documentation/Splunk/9.4.2/Installation/HowtoupgradeSplunk which states to update to 9.4 you need to be on 9.1/9.2.
To upgrade to 9.2 from 8.1.x you first need to upgrade to 9.0 (See https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/9.2/upgrade-or-migrate-...)
Therefore your upgrade path should be 8.1.14 -> 9.0.9 -> 9.2.8 -> 9.4.x
You can get older binaries/packages as required by using https://github.com/livehybrid/downloadSplunk or I can add them here if you let me know which packages you need.
As @PrewinThomas mentioned, another option would be to copy the configuration from the 8.1 server to a new installation using 9.4 *however* please note that this really depends on your configuration and generally is only advised for forwarders, even then any checkpoint data for any inputs or KV stores may mean you face issues with re-ingesting data or failed data collections. If you are upgrading SH/IDX then I would strongly suggest following the supported upgraded path as there are changes to things like the indexes which cannot be made manually.
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing
Hello @livehybrid
I’m sincerely grateful for your response. Your links were very helpful — I was able to locate all the versions I needed for my test environment. Thank you.
May I ask—in your experience, have there been situations where a Heavy Forwarder (HF) was running a significantly higher version than the indexers?
Specifically, I plan to run my HF on at least version 9.2, up to 9.4. However, I’m not sure how well that will work with my indexers on version 8.2.12. My HF is used only for HEC (HTTP Event Collector).
Hi @igor5212
Ive generally not found any issues with HFs running a higher version of Splunk compared with the indexers. There is a good compatibility table at https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/compatibility-matrix/splunk-p... which lists the officially supported combinations of HF->IDX versions
Which versions are your HF and IDX running?
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing
I think the in most cases there are no real issues with different versions as long as there is no too big cap with versions. And as/if you are using only HEC to sending events from HF->IDX then it shouldn't be issue. But if you are using also s2s then there could be some challenges. And at least MC gives you a warnings if HFs are added there and those are newer than MC itself.
If you will need help from Splunk Support then this could be issue as that combination is not officially supported.
Anyhow you should update at least 9.2.x or 9.3. asap. Here is link to support times for Splunk core https://www.splunk.com/en_us/legal/splunk-software-support-policy.html#core
With earlier versions the rule was that indexers must be the newest versions. HFs and UFs which were connected can be lower. And same for UF vs HF. This has been changed with 9.x (maybe x was 3 or 2, I cannot remember exact version). After your indexers and cm are that level HFs and UFs can be newer than indexers and CM and other splunk servers.
So in your situation when you have 8.x.x all HFs and UFs should be max same version than those servers are.
Anyhow those versions are already out of support, so you should upgrade those as soon as possible to supported version. Probably 9.4.4 is currently best option. Don’t go to 10.0.0 as it’s too new for production use!
Hi @igor5212 ,
upgrading from Splunk 8.1.14 to 9.4 is supported, as Splunk supports direct upgrades between any two minor/patch versions, provided you follow upgrade best practices. However, for testing purposes, you’ll need to get a copy of Splunk 8.1.14, and unfortunately, it’s not listed on the public Splunk downloads page anymore, as they tend to remove older versions.
Please reach out to Splunk Support for the older version
https://splunk.my.site.com/customer/s/need-help/create-case
backup Splunk_HOME/etc folder and $Splunk_home/var/lib/splunk before procedding
Check the Python 3 compatibility for the scripts and addons in the HF
Hi @thahir
This information is incorrect, also this isnt two minor/patch versions, its a major version (8->9).
Interestingly if you ask several AI models the same question it also says that its supported (and sometimes links to the upgrade page that says it isnt!) - Im not saying your response was from an AI response as such, but its easy for mis-information to spread as truth which is why I'm pointing this out.
For clarity - the supported upgrade path should be 8.1.14 -> 9.0.9 -> 9.2.8 -> 9.4.x.
See https://docs.splunk.com/Documentation/Splunk/9.4.2/Installation/HowtoupgradeSplunk and https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/9.2/upgrade-or-migrate-...
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing
You can request access to older versions directly through the support portal.
Also as a workaround(if you are not getting older version) you can copy your existing splunk 8.1.x to a new server and removing log folder path(to minimize size) and modify server.conf, web.conf, and any relevant .conf files.
Mainly,
-Change hostname, GUID, and management port if needed.
-Update inputs.conf and outputs.conf to reflect test environment.
-Disable or redirect any production data flows
Regards,
Prewin
Splunk Enthusiast | Always happy to help! If this answer helped you, please consider marking it as the solution or giving a Karma. Thanks!