Splunk

 

1Introduction

Splunk is an enterprise software that makes machine data accessible, usable and valuable to anyone. Splunk makes it simple to collect, analyse, and act upon the value of the data generated by an enterprise’s technology infrastructure. Splunk helps users turn machine data into operational intelligence.

Such a powerful tool requires reliable and powerful support. The KEMP LoadMaster delivers an exceptional, cost-effective and easy to use solution that, by employing Adaptive Load Balancing, balances requests across Splunk servers.

When deployed as a pair, two LoadMasters give the security of High Availability (HA). HA allows two physical or virtual machines to become one logical device. Only one of these units is ever handling traffic at any particular moment. One unit is active and the other is a hot standby (passive). This provides redundancy and resiliency, meaning if one LoadMaster goes down for any reason, the hot standby can become active, therefore avoiding any downtime. For more information on HA please refer to: High Availability (HA), Feature Description.

1.1Document Purpose

This document provides guidance on how to deploy Splunk with a KEMP LoadMaster. The KEMP Support Team is available to provide solutions for scenarios not explicitly defined.

The KEMP support site can be found at: https://support.kemptechnologies.com.

1.2Intended Audience

This document is intended to be used by anyone deploying Splunk with a KEMP LoadMaster.

2Splunk Template

KEMP has developed a template containing our recommended settings for Splunk. This template can be installed on the LoadMaster and used when creating Virtual Services. Using a template automatically populates the settings in the Virtual Services. This is quicker and easier than manually configuring each Virtual Service. If needed, changes can be made to any of the Virtual Service settings after using the template.

Download released templates from the Templates section on the KEMP documentation page: http://kemptechnologies.com/documentation/.

For more information and steps on how to import and use templates, refer to the Virtual Services and Templates, Feature Description.

For steps on how to manually add and configure each of the Virtual Services, refer to the Configure Splunk Virtual Services section of this document.

3Architecture

Figure 3‑1: Splunk Deployment Architecture

4Configure Splunk Virtual Services

The environment in which Splunk is deployed determines which of the following setups should be used.

4.1Enable Subnet Originating Requests Globally

It is best practice to enable the Subnet Originating Requests option globally.

In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet) Subnet Originating Requests is usually not needed. However, enabling Subnet Originating Requests should not affect the routing in a one-armed setup.

In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real Servers are on network B - Subnet Originating Requests should be enabled on LoadMasters with firmware version 7.1-16 and above.

When Subnet Originating Requests is enabled, the LoadMaster will route traffic so that the Real Server will see traffic arriving from the LoadMaster interface that is in that network/subnet.

When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual Services. If the Subnet Originating Requests option is disabled globally, you can choose whether or not to enable Subnet Originating Requests on a per-Virtual Service basis.

To enable Subnet Originating Requests globally, follow the steps below:

  1. In the main menu of the LoadMaster WUI, go to System Configuration > Miscellaneous Options > Network Options.

Figure 4‑1: Subnet Originating Requests

  1. Tick the Subnet Originating Requests check box.

4.2Splunk Virtual Service

The following are the steps involved and the values required to configure Splunk Virtual Service:

  1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services> Add New.

Figure 4‑2: Virtual Services Parameters

  1. Enter a valid IP address in the Virtual Address text box.
  2. Enter 443 in the Port text box.
  3. Enter a recognizable Service Name, for example Splunk.
  4. Ensure tcp is selected as the Protocol.
  5. Click Add this Virtual Service.
  6. Enter the details shown in the following table:

Section

Option

Value

Comment

Standard Options

Transparency

Deselected

 
 

Persistence Mode

None

 
 

Scheduling Method

Round robin

 

SSL Properties

SSL Acceleration

 

 

 

 

Enabled

Reencrypt

 

 

A wildcard certificate allows secure connections to be established with a request URL in the format of *.example.com. With this approach, a single certificate secures traffic for all clients in a multi-tenant environment.

 

Supported Protocols

TLS1.0

TLS1.1

TLS1.2

 
 

Cipher Set

Best Practices

For further information on cipher sets, please refer to the SSL Accelerated Services, Feature Description.

Advanced Properties

Content Switching

Disabled

 
 

Add HTTP Headers

 

Legacy Operation (X-ClientSide)

 
 

Redirect URL

https://%h%s

Click Add HTTP Redirector

Real Servers

Real Server Check Method

HTTPS Protocol

 
 

Checked Port

8000

 
 

HTTP Method

HEAD

 

Table 1: Splunk Virtual Service Settings

Users should note that clicking the Set Redirect URL button, automatically creates a redirect Virtual Service on Port 80.

  1. Add the Real Servers:

a)Click the Add New button.

b)Enter the IP address of the AX Server.

c)Enter 443 as the Port.

The Real Server Port should match the Virtual Service Port.

The Forwarding method and Weight values are set by default. An administrator can change these.

d)Click Add this Real Server. Click OK to the pop-up message.

e)Repeat steps b) to d) above to add more Real Servers as needed, based on the environment.

4.3Splunk HTTP (Redirect) Virtual Service

This Virtual Service is automatically created when users click the Set Redirect URL button while configuring the Splunk Virtual Service in Section 4.2.

4.4Splunk Syslog UDP Virtual Service

The following are the steps involved and the values required to configure the Splunk Syslog UDP Virtual Service:

  1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services> Add New.

Figure 4‑3: Virtual Services Parameters

  1. Enter a valid IP address in the Virtual Address text box.
  1. Enter 514 in the Port text box.
  2. Enter a recognizable Service Name, for example Splunk Syslog udp.
  3. Ensure udp is selected as the Protocol.
  4. Click Add this Virtual Service.
  5. Enter the details shown in the following table:

Section

Option

Value

Comment

Standard Options

Transparency

Enabled

 
 

Persistence Mode

Source IP Address

 
 

Prersistence Timeout

1 Minute

 
 

Scheduling Method

Weighted round robin

 

Real Servers

Real Server Check Method

ICMP Ping

 

Table 2: Splunk Syslog UDP Virtual Service Settings

  1. Add the Real Servers:

a)Click the Add New button.

b)Enter the IP address of the AX Server.

c)Enter 514 as the Port.

The Real Server Port should match the Virtual Service Port.

The Forwarding method and Weight values are set by default. An administrator can change these.

d)Click Add this Real Server. Click OK to the pop-up message.

e)Repeat steps b) to d) above to add more Real Servers as needed, based on the environment.

References

Unless otherwise specified, the following documents can be found at: http://kemptechnologies.com/documentation.

Virtual Services and Templates, Feature Description. High Availability (HA), Feature Description SSL Accelerated Services, Feature Description

Document History

Date

Change

Reason for Change

Version

Resp.

July 2016

Initial Draft

First draft of document

1.0

KG

Was this article helpful?

0 out of 0 found this helpful

Comments