Getting Data In

Running Splunk Forwarder on port other than 8089

beaunewcomb
Communicator

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?

Tags (1)
1 Solution

jbsplunk
Splunk Employee
Splunk Employee

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.

View solution in original post

jbsplunk
Splunk Employee
Splunk Employee

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.

View solution in original post

lakshman237
Path Finder

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)

0 Karma
.conf21 Now Fully Virtual!
Register for FREE Today!

We've made .conf21 totally virtual and totally FREE! Our completely online experience will run from 10/19 through 10/20 with some additional events, too!