|
What are the implications of running the splunk forwarder on a non-standard port? Do I have to change anything in the deployment server to look for deployment clients on a different port? Or am I going to see normal behavior without any other changes whatsoever? |
|
You'll need to add a web.conf file in your custom apps $SPLUNK_HOME/etc/apps/deploymentapps/appname/system/local/ folder. You can put the configuration there: mgmtHostPort = x.x.x.x:8090 As long as your deployment server continues to listen on the same management port and you've defined that in your deploymentclient.conf file, you should be fine. Agree with jbsplunk. the forwarder can run on a port other than 8089. However, it should be able to connect to deployment server on the mgmt port and for making things simpler, the mgmt of deployment server should be same as that of the other splunk nodes (search heads and indexers)
(10 Jul '12, 15:33)
lakshman237
|
