DHCP on Splunk UF

[inventsekar]

Hi, let's say we got around hundred UF's which are DHCP (their hostname and/or ip address changes often)
1. From UF's perspective, nothing changes. It will send logs to indexers, it will poll the deployment server as usual. Is that correct?!
2. At indexer, i think, events will be still having the old UF hostname/ip address, right?
3. What will happen at the deployment server?

I searched for these dhcp issues, but didn't get answers. Thanks

[solarboyz1 · Accepted solution]

1. From UF's perspective, nothing changes. It will send logs to indexers, it will poll the deployment server as usual. Is that correct?!

Correct.

2. At indexer, i think, events will be still having the old UF hostname/ip address, right?

When Splunk gets installed, it will try to create a outputs.conf with the line hostname=*
That value will be used as the default hostname for events from the UF, regardless of DHCP changes

3. What will happen at the deployment server?

Deployment server will use the GUID and hostname to track the clients checking in. It should not be effected by DHCP.

[inventsekar]

Thanks for your response..
Let's say the hostname of a UF got changed.
And the deployment server will still be able to identify the UF with its new hostname and the GUID ah?!?!

[solarboyz1]

Splunk will not recognize the hostname change, it will continue to use the outputs.conf hostname value.

If the outputs.conf hostname changes, I believe you will get see two records on the deployment server and will need to delete the old entry. (Or not, it really doesnt impact anything).

If you use the hostname to identify which serverclass a host falls into, you would need to fix that.

[inventsekar]

That's great, thx.. will test this once on Monday and accept this answer... Thanks again