Installation

Indexer unreachable after upgrade from 6.3.3. to 7.3.3

jeffreywels
New Member

Hi all,

I just upgraded my indexer from 6.3.3. to 7.3.3.
The server seems to be up (as in i can log in), but it does show up as "unreachable" in de cluster overview next to another indexer which hasn't been updated.

Before the update, nothing was wrong.

Why could this happen?

The only error that i see appear is "ERROR AdminManager - Argument "generation_id" is not supported by this handler." which comes form the master environment, and showed up after upgrading the indexer. So this might be related.

Could this be to the fact that the master environment is still on version 6.3.3?

Best regards,
Jeffrey

Labels (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

The cluster master is supposed to be upgraded before the indexers are upgraded. Also, all indexers should be upgraded at the same time. See https://docs.splunk.com/Documentation/Splunk/8.0.0/Indexer/Upgradeacluster#Upgrade_a_6.x_or_higher_i...

---
If this reply helps you, Karma would be appreciated.
0 Karma

oscar84x
Contributor

Hi Jeffrey. There's a very specific procedure for this. The master is the first one that needs to be upgraded, followed by the search head(s) and ALL search peers. The ink below gives you all the steps specifically for upgrading from 6.x and higher:

https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Upgradeacluster#Upgrade_a_6.x_or_higher_...

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...