topic Re: Monitor Cyberoam 35iNG in Security

Monitor Cyberoam 35iNG

nilesh8 — Mon, 26 Aug 2013 12:00:06 GMT

Hi All,

How to configure splunk 5.0 to monitor Cyberoam 35iNG firewall.

Re: Monitor Cyberoam 35iNG

rturk — Mon, 26 Aug 2013 12:12:54 GMT

Hi nilesh8.

I'm not familiar with that particular firewall, but I'm assuming that it is capable of sending Syslog messages.

You can configure Splunk to accept Syslog messages by following the steps in this link: http://docs.splunk.com/Documentation/Splunk/5.0.4/Data/SyslogUDP

Hope this helps 🙂

Re: Monitor Cyberoam 35iNG

nilesh8 — Mon, 26 Aug 2013 12:36:52 GMT

Hi Turk,
Thanks for reply. I have configured it via syslog udp port 514. But i am not able to see any logs in splunk also not show the connection in 'netstat' command.

Re: Monitor Cyberoam 35iNG

rturk — Mon, 26 Aug 2013 12:40:05 GMT

A few things I'd check:
- Ensure Syslog is being sent by TCP not UDP
- Temporarily disable the server firewall on the Splunk server to see whether that's a factor

Re: Monitor Cyberoam 35iNG

nilesh8 — Mon, 26 Aug 2013 13:46:37 GMT

I have configured it by TCP port and also disabled server firewall but still not see any logs on splunk

Re: Monitor Cyberoam 35iNG

rturk — Mon, 26 Aug 2013 13:50:22 GMT

Ahhh one other point I forgot to mention, have you confirmed that Splunk is set up to receive TCP 514?
- Manager > Data Inputs > TCP > Add New
You might want to do the same for UDP just to be sure.

Re: Monitor Cyberoam 35iNG

nilesh8 — Mon, 26 Aug 2013 14:20:57 GMT

I have configured it with TCP 514 only
TCP port = 514
Source type = syslog
Status = Enabled

Re: Monitor Cyberoam 35iNG

nilesh8 — Mon, 26 Aug 2013 14:31:43 GMT

I have configured it via tcp and udp port 514 still i am waiting for logs.

Re: Monitor Cyberoam 35iNG

rturk — Tue, 27 Aug 2013 00:36:00 GMT

My only other suggestions at this point would be to narrow down the possible cause:
- Redirect a device/server with a known-good syslog generation at Splunk
- Point your firewall at a known/good syslog collector
- Look at the event in $SPLUNK_HOME/var/log/splunk/splunkd.log to see any potential issues

Everything you've mentioned indicates you've set it up correctly, so it's time for troubleshooting now 🙂

Re: Monitor Cyberoam 35iNG

nilesh8 — Wed, 28 Aug 2013 06:00:51 GMT

I have found following entries in splunk log
08-26-2013 04:22:05.656 -0700 INFO TcpInputConfig - performing DNS lookup on 192.168.2.1

Also i tried it to configure via SNMP and found below log
CarrierError: bind() for (u'192.168.2.1', 162) failed: [Errno 10049] The requested address is not valid in its context