Splunk® OVA for VMware and NetApp

Splunk OVA for VMware

Acrobat logo Download manual as PDF


This documentation does not apply to the most recent version of Splunk® OVA for VMware and NetApp. For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

What is new

See the Fixed and known issues page for changes made for this release.

Note:

Versions 3.4.0 and above includes the following updates.

  • The number of CPU cores has increased to 8, and the amount of RAM has increased to 12 GB.
  • OVA runtime user has changed from splunkadmin to splunk. Users need to login into their OVA as splunk, instead of splunkadmin.
  • The Splunk platform file located in the Splunk OVA for VMware and NetApp is installed using an .rpm package, replacing the .tgz package.
  • The Splunk OVA for VMware and NetApp runs the Splunk platform from /opt directory instead of /home/splunkadmin/opt.
  • The kvstore service has been disabled for the Splunk OVA for VMware. It is not needed on heavy forwarders.

Versions 3.4.0 and above of this product includes the following root user CLI packages.

  • system-config-network-tui. A text user interface that can be used to configure DCNs with a fixed IP address and hostname. system-config-network-tui
  • telnet. Used to check port availability using telnet commands. telnet <host> <port>
  • bind-utils. Used to test network connectivity. dig @dns hostname
Last modified on 07 July, 2017
PREVIOUS
Troubleshooting
  NEXT
Fixed and known issues

This documentation applies to the following versions of Splunk® OVA for VMware and NetApp: 3.4.0


Was this documentation topic helpful?


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