All Apps and Add-ons

Can I install the DCN on same machine as my Search Head?

halr9000
Motivator

Is there a single-server installation model? I.e. can the DCN be installed on the same host that's also the SH + Indexer, and are there any gotchas? The docs clearly state "multiple machines", but that can be a burden, especially for a small environment, proof-of-concept or a lab.

1 Solution

tfletcher_splun
Splunk Employee
Splunk Employee

Yes there is a way to install a single box installation. But first, As a disclaimer, the resources involved in collecting data often make it a poor choice to colocate with a search head or indexer. There are no sizing guidelines for a single box installation and if call support for any issues the first thing you will be asked to do is to move data collection to another machine. Now that that is over on to the how to do it.

The Splunk App for NetApp Data ONTAP utilizes the Hydra data collection framwork (that's that SA-Hydra app that ships with it). It follows a fairly ordinary client server paradigm if you consider the scheduler node (typically run at the search head) the client and the data collection nodes as servers with data collection services. So to install on a single box you need simply make that box both the client and the server. This amounts to a normal install except that when you come to the add data collection nodes step you simply add the splunk instance you are configuring the scheduler on as its own data collection node. Thus your data collection node's management URI would be along the lines of https://localhost:8089.

Note there is also a security concern with this methodology as this machine will have its own service account stored for logins. With that and the resourcing concern I would really only do this for as simple a POC as possible and never in production.

View solution in original post

tfletcher_splun
Splunk Employee
Splunk Employee

Yes there is a way to install a single box installation. But first, As a disclaimer, the resources involved in collecting data often make it a poor choice to colocate with a search head or indexer. There are no sizing guidelines for a single box installation and if call support for any issues the first thing you will be asked to do is to move data collection to another machine. Now that that is over on to the how to do it.

The Splunk App for NetApp Data ONTAP utilizes the Hydra data collection framwork (that's that SA-Hydra app that ships with it). It follows a fairly ordinary client server paradigm if you consider the scheduler node (typically run at the search head) the client and the data collection nodes as servers with data collection services. So to install on a single box you need simply make that box both the client and the server. This amounts to a normal install except that when you come to the add data collection nodes step you simply add the splunk instance you are configuring the scheduler on as its own data collection node. Thus your data collection node's management URI would be along the lines of https://localhost:8089.

Note there is also a security concern with this methodology as this machine will have its own service account stored for logins. With that and the resourcing concern I would really only do this for as simple a POC as possible and never in production.

View solution in original post

Register for .conf21 Now! Go Vegas or Go Virtual!

How will you .conf21? You decide! Go in-person in Las Vegas, 10/18-10/21, or go online with .conf21 Virtual, 10/19-10/20.