Reporting

Help to retrive splunk server ip

stcs
Engager

Hi

I would like to send the logs generated by the wireless lan controller to splunk. I received the url with port from splunk to send the data, but the controller only accpets IP addresses in the syslog server box.

If there a way to find the ip address for the URL. Tried using the ip return when sending ping request to the server but it does not seem to be working.

Please advise.

Thanks in advance.

Tags (1)
1 Solution

jbsplunk
Splunk Employee
Splunk Employee

Yes, you could do something like 'ifconfig -a' if you're using a linux box, or 'ipconfig -all' if you're using windows, and you can see the ip addresses of the network devices on the splunk server. You could also use something like nslookup from the remote side to see what dns thinks the address of the server is:

'nslookup mysplunk.domain.com'

This is really just a matter of using the network utilities that come with your operating system.

View solution in original post

jbsplunk
Splunk Employee
Splunk Employee

Yes, you could do something like 'ifconfig -a' if you're using a linux box, or 'ipconfig -all' if you're using windows, and you can see the ip addresses of the network devices on the splunk server. You could also use something like nslookup from the remote side to see what dns thinks the address of the server is:

'nslookup mysplunk.domain.com'

This is really just a matter of using the network utilities that come with your operating system.

Get Updates on the Splunk Community!

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...

Splunk APM: New Product Features + Community Office Hours Recap!

Howdy Splunk Community! Over the past few months, we’ve had a lot going on in the world of Splunk Application ...

Index This | Forward, I’m heavy; backward, I’m not. What am I?

April 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...