Security

changing Indexer receiver port

Rajshekhar
New Member

We have indexer installed on windows server which is connected to many forwarders(linux servers).
Right now we are using port 9997 as receiver port in Indexer server, we have lots of data in indexer.

Now we need to change the receiver port from existing 9997 to some other port.

1)after changing the port in Splunk indexer, will I be able to search all the past data which was indexed using port 9997?

2)Will I get latest data using new port without any issues?

3)Are there any special modifications we need to do for this to work properly?
Please let me know how I can change the port without causing any issues in existing data.

Thanks|

Tags (2)
0 Karma

Takajian
Builder

I answer your question inline as bellow.

1)after changing the port in Splunk indexer, will I be able to search all the past data which was indexed using port 9997?

Yes. The past data is already stored in index server, you can search them without problem.

2)Will I get latest data using new port without any issues?
Yes, you can get data with new port. But you need to change configuration of all forwarders. If you use deployment server, you can deploy new configuration to all forwarder easily. If not, you need to change them manually.

3)Are there any special modifications we need to do for this to work properly?
Please let me know how I can change the port without causing any issues in existing data.

It does not affect existing data. Most problem I think is to change configuration of all forwarders.

Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...