Getting Data In

Logs from Firepower not indexing in Splunk

Hugo
Engager

Hi All,

We have two splunk environments 8.2, and I am in charge of these two. On the first environment, everything works fine. I'm trying to configure the same thing on the second for another infrastructure.

To explain a little : I have two heavy forwarders behind a VIP, and then logs are forwarded to an indexer cluster of two indexers.

I had configure some syslog forwarding for network devices, and everything works fine in TCP or UDP, my logs are showing in the Search Head, in the good index.

But for Firepower, impossible to indexing datas, I use TCP 10000 and with a tcpdump on the HF I see logs arrives, but after that nothing...

I've checked splunkd.logs (and nearly all log file on the servers), there are no errors on the HF or the Indexers and nothing is blocked by a firewall or the network.

I don't use estreamer add-on and firepower add-on, and on the first infrastructure is working fine in the same configuration.

Here are some configurations :

On Indexers :

[fw_ext]
homePath = volume:primary/fw_ext/db
coldPath = volume:primary/fw_ext/colddb
thawedPath = $SPLUNK_DB/fw_ext/thaweddb
repFactor = auto
maxHotBuckets=10

On HF :

[tcp://10000]
index = fw_ext
sourcetype = cisco:asa
connection_host = ip
disabled = 0

Paths are empty for the index fw_ext, so I presume that the logs don't arrives to the Indexers.

On the Firepower, configuration for the first and the second infrastructures are identical, so I presume that the problem don't come from the device too.

The forwarding configuration is good too since it works for every other network devices and servers.

 

Have you guys any ideas ?

Thanks by advance.

Labels (3)
Tags (3)
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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...