Deployment Architecture

Need steps to migrate from old deployment server to new deployment server

sumitkathpal
Explorer

Dear Experts,

we have around 40 UF installed and pointing to old deployment server, Help is required we want UF point to new heavy forwarder.

On which files we need to make changes via old deployment server so that it point to new deployment server.

Thanks in advance.

0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi sumitkathpal,
In Splunk Community, you can find many similar questions in the past weeks (e.g. https://answers.splunk.com/answers/575569/is-there-an-easy-way-to-redirect-existing-universa.html#an... ).

The problem is that deploymentclient.conf is located in $SPLUNK_HOME/etc/system/local) and this folder isn't managed by Deployment Server.

Anyway, the easiest way is (if possible) that you use the same IP Address in the new Deployment server so client addressing (file deploymentclient.conf) remain the same.

If this easy solution isn't possible the only choice is to run a remote script ( %SPLUNK_HOME/bin/splunk set deploy-poll xxx.xxx.xxx.xxx:8089 ) or use a software distribution system to run the same command or updated deploymentclient.conf file.

Bye.
Giuseppe

View solution in original post

lfedak_splunk
Splunk Employee
Splunk Employee

Hey @sumitkathpal, If @cusello answered your question please accept his answer to close the post and to award karma points. Good luck with your deployment migration!

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi sumitkathpal,
In Splunk Community, you can find many similar questions in the past weeks (e.g. https://answers.splunk.com/answers/575569/is-there-an-easy-way-to-redirect-existing-universa.html#an... ).

The problem is that deploymentclient.conf is located in $SPLUNK_HOME/etc/system/local) and this folder isn't managed by Deployment Server.

Anyway, the easiest way is (if possible) that you use the same IP Address in the new Deployment server so client addressing (file deploymentclient.conf) remain the same.

If this easy solution isn't possible the only choice is to run a remote script ( %SPLUNK_HOME/bin/splunk set deploy-poll xxx.xxx.xxx.xxx:8089 ) or use a software distribution system to run the same command or updated deploymentclient.conf file.

Bye.
Giuseppe

sumitkathpal
Explorer

Thanks @cusello.

You mean i can run the command on splunk deployement server %SPLUNK_HOME/bin/splunk set deploy-poll xxx.xxx.xxx.xxx:8089 ) where xx.xx.xx.xx is new deployment server IP .

above query will help to re-direct to new deployment IP?

0 Karma

gcusello
SplunkTrust
SplunkTrust

No you have to connect in remote ssh session from an enabled server on the target servers and run this command on each target server.
For this reason I spoke of script because, if you have many servers, it's so long!
the other choice is to copy the new deploymentclient.conf (the one that addresses the new Deployment Server) into the $SPLUNK_HOME/etc/system/local folder of each target server.
In both the cases you have to restart Splunk.

In other words, script should be something like this:
ssh -q -l root $hostname
ssh -q -l root $hostname "/opt/splunkforwarder/bin/splunk set deploy-poll xx.xxx.xxx.xx:8089 -auth admin:changeme"
ssh -q -l root $hostname "/opt/splunkforwarder/bin/splunk restart"

Bye.
Giuseppe

0 Karma
Get Updates on the Splunk Community!

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...