Getting Data In

Not receiving readable logs from Brocade Switches

nairv
Explorer

We have added brocade switches to heavy forwarder via tcp:6514. We are able to receive the logs , but not in a readable format.

\x00a\x00\x00]"e8H,W\xCC\xA7az\xB9\xFF\xFB \xFE\x9E\x8C
֋\xC5\xCBhQ\x8E\xD1a{\x00\x00 \x00=\x005\x00<\x00/\x00
\x00\xFF\x00\x00(\x00#\x00\x00\x00
\x00 \x00

input.conf
[tcp://6514]
connection_host = dns
index = san
sourcetype = BROCADE_SWITCH

settings in Brocade switch

-secure -port 6514 to the syslogadmin --setip cmd

Switch type
2 model type 6520's
4 model type 5480
2 model- bvlfcsw100/200

Tags (1)
0 Karma
1 Solution

nairv
Explorer

The brocade switch has to be always pointed to UDP 514 in HF or UF. If we point towards any other port like how I was using TCP 6514 we receive only encrypted data and non readable since it becomes secured port.

View solution in original post

0 Karma

nairv
Explorer

The brocade switch has to be always pointed to UDP 514 in HF or UF. If we point towards any other port like how I was using TCP 6514 we receive only encrypted data and non readable since it becomes secured port.

0 Karma

nairv
Explorer

The issue has been solved now I am able to get readable logs from the brocade..

0 Karma

adonio
Ultra Champion

@nairv please share what you did to solve your challenge so others can learn

0 Karma
Get Updates on the Splunk Community!

Splunk Enterprise Security: Your Command Center for PCI DSS Compliance

Every security professional knows the drill. The PCI DSS audit is approaching, and suddenly everyone's asking ...

Developer Spotlight with Guilhem Marchand

From Splunk Engineer to Founder: The Journey Behind TrackMe    After spending over 12 years working full time ...

Cisco Catalyst Center Meets Splunk ITSI: From 'Payments Are Down' to Root Cause in ...

The Problem: When Networks and Services Don't Talk Payment systems fail at a retail location. Customers are ...