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!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...