Installation

How to use License Pooling between two Splunks that has no communication in between?

bilgin
New Member

We have two higly secure Datacenters that has no communication in each other. They both connect to the internet but due to high security it is not allowed to intsall a Public Splunk and use it as a Master in elsewhere. Is there a solution or workaround to use the License Pooling under this scenario?

0 Karma
1 Solution

kristian_kolb
Ultra Champion

Not as far as I know.

The license master and license slave(s) must be able to communicate on port 8089 (by default). If you don't want to set up a VPN connection between the two splunk servers (you could do this on dedicated NIC in each server for this purpose alone), you'd have to split your license into two separate license files, and use them independently of each other.

Hope this helps,

Kristian

View solution in original post

kristian_kolb
Ultra Champion

Not as far as I know.

The license master and license slave(s) must be able to communicate on port 8089 (by default). If you don't want to set up a VPN connection between the two splunk servers (you could do this on dedicated NIC in each server for this purpose alone), you'd have to split your license into two separate license files, and use them independently of each other.

Hope this helps,

Kristian

gkanapathy
Splunk Employee
Splunk Employee

just to clarify, you would have to contact splunk support to split your license into two half-size licenses. note that they will not be "pooled" in this case, so if you have 100 GB total, you split it into 2x50GB licenses, and then one of the servers indexed 75 GB while the other only did 10 GB, you'll get a violation on the 75 GB.

jbsplunk
Splunk Employee
Splunk Employee

Exactly correct.

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...