Getting Data In

On a Syslog Split Port implementation, should I split ports on heavy forwarders also?

jacauc
Explorer

I have a layered network with the bulk of the Splunk infrastructure in Zone 1 (Indexer, Collector, Search Head)

Within this zone, I'm using split UDP ports to direct specific syslog traffic to appropriate indexes for example:

 

Palo Alto Syslog : Indexer IP: UDP/5140 which ends up in Palo Alto Index

Cisco Cisco: Indexer IP: UDP/5141 which ends up in Cisco Index

iDRAC / iLO: Indexer IP: UDP/5142 which ends up in iDRAC/iLO index.

etc....

 

In other network zones, Zone 2, 3, 4 etc I have a Heavy Forwarder which allows for devices in these zones to funnel their traffic via the HF to the Indexer (Only communication across firewall between zones are HF to Indexer and no other direct communication from hosts in Zones to Indexer in Zone 1 allowed)

 

Should I configure my HF to also have the same data inputs (ports 5140, 5141, 5142 etc) and also configure devices in these Zones to point to those ports, or should devices in Zones 2,3,4 simply send to UDP 514 and when it reaches the indexer it will be split up appropriately?

 

I'm guessing the data inputs should look the same on all HFs as in the Indexer. Can anyone confirm?

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

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)

Hello Splunkers,   So you searched, “what is the name of the usb key inserted by bob smith?”  Not gonna lie… ...

Automating Threat Operations and Threat Hunting with Recorded Future

    Automating Threat Operations and Threat Hunting with Recorded Future June 29, 2026 | Register   Is your ...