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.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...