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!

Shape the Future of Splunk: Join the Product Research Lab!

Join the Splunk Product Research Lab and connect with us in the Slack channel #product-research-lab to get ...

Auto-Injector for Everything Else: Making OpenTelemetry Truly Universal

You might have seen Splunk’s recent announcement about donating the OpenTelemetry Injector to the ...

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...