Documentation: 3.0.2
|  Print Version Contents
This page last updated: 10/29/07 03:10pm

Configure deployment clients

At this point, you should have determined which server classes each client belongs to and which discovery method (polling or multicast) each will use.

You will now install Splunk on each client machine and configure it as a deployment client.

  • Do a normal Splunk install. (You will probably run a script to install it on a each machine.)
  • Set up each client to poll for configurations.

Enable the client and server

You can enable the client and server from Splunk's CLI. To use Splunk's CLI, navigate to the $SPLUNK_HOME/bin/ directory and use the ./splunk command. You can also add Splunk to your path and use the splunk command.

From the Splunk CLI, run the following command:

./splunk set deploy

This will enable the client module and allow it to communicate with the deployment server.

Polling method

If you decide to use the polling method, run the following command from the Splunk CLI on each client:

./splunk set deploy-poll x.x.x.x:pppp

Substitute the ip number and management port of the deployment server (the management port is typically 8089).

Multicast discovery method

If you decide to use multicast, run the following command from the Splunk CLI on each client:

./splunk set deploy-multicast x.x.x.x:pppp

Substitute the multicast group IP/Port.

Sync the server and client

Now you are read to sync the server with the clients.

Start the deployment server from its Splunk CLI:

./splunk start

Start the deployment clients from their Splunk CLIs. Use this command to start Splunk without a license prompt:

./splunk start --accept-license

At this point, every client will either pick up the multicast packet as sent out by the deployment server or will poll the deployment server. Each client will then determine that it does not have up to date configurations and will ask the deployment server for a bundle file for each server class that it is a member of. Once it receives these bundle files, it will restart itself using the new configurations it has now received.

Previous: Configure a Splunk Deployment Server    |    Next: Configuration changes after initial deployment

Comments

No comments have been submitted.

Log in to comment.