Splunk® OVA for VMWare and NetApp

Splunk OVA for VMware

Download manual as PDF

Download topic as PDF

About the Splunk OVA for VMware

The Splunk OVA for VMware is a preconfigured virtual machine with a lightweight operating system, Splunk heavy forwarder and all necessary add-ons and supporting add-ons for scheduling collection of inventory and performance data from VMWare vCenter servers. The Splunk OVA for VMware deploys as a Data Collection Node (DCN) to collect data for the Splunk IT Service Intelligence Virtualization Module and the Splunk App for VMware.

DCNs are required components for any Splunk App for VMware or Splunk IT Service Intelligence Virtualization Module deployment. Users can use the Splunk OVA for VMware to deploy a DCN but users can set up a DCN without the Splunk OVA for VMware by following the directions in the Create your own data collection node section of the Install the Splunk OVA for VMware section of this manual.

Requirements

The Splunk OVA for VMware contains:

  • Virtual Hardware v7
  • CentOS v6.4
  • Disk Size 16gb
  • VMWare Tool v5.1
  • A Splunk Enterprise v6.4.4 heavy forwarder
  • Splunk Addon for VMWare 3.3.2 (includes Splunk_TA_vmware, SA-Hydra version 4.0.2, SA-VMNetAppUtils version 1.0.0)

The Splunk OVA for VMware comes with two default user accounts:

  • The administrator account, with the credentials splunkadmin/changeme.
  • The root user account, with the credentials root/changemenow.

The data collection node (DCN) deployment has the following default configuration:

  • Four cores. 4 vCPUs or 2 vCPUs with two cores with a reservation of 2GHz.
  • 6GB memory with a reservation of 1GB.
  • 10-12GB of disk space.

The data collection node (DCN) scheduler must be deployed on a dedicated search head, and not on any individual search head in a search head cluster.

  NEXT
Install the Splunk OVA for VMware

This documentation applies to the following versions of Splunk® OVA for VMWare and NetApp: 3.3.2


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters