Deployment Architecture

Changing deployment server IP

andreac81
Explorer

Hi to all,
I had a deployment server (server A), an indexer/search head (server B) and some monitored servers.
I copied the folder deployment-apps by deployment server to indexer and deleted the deployment server (deleted server A and used server B as deployment, indexer and search head)

In each monitored server I manually changed in /opt/splunkforwarder/etc/system/local/deploymentclient.conf the
targetUri IP.

I restarted splunk server (server B) , in forwarder management I see "No clients phoned home".
what is missing?

0 Karma

andreac81
Explorer

Hi,

  • I upadated the serverclass.conf I
    haven't deploymentclient.conf Firewall rules are OK

I have indexer/search head with Splunk 6.6.2 while the forwarders use Splunk 6.4, can it be a problem?

Thanks,
Andrea

0 Karma

santiagoaloi
Path Finder

You might have forgotten to copy the serverclass.conf to the new deploymentserver.
did you restart the forwarders? - otherwise the deploymentclient.conf changes wont be updated.
Did you specify the port after the new deployment server IP, check for firewall rules, port 8089 should be open in your deployment server.

Take a look here:

https://answers.splunk.com/answers/295845/how-to-troubleshoot-why-a-deployment-client-is-una.html

0 Karma
Get Updates on the Splunk Community!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...