Splunk® Supported Add-ons

Splunk Add-on for NetApp Data ONTAP

Manage your ONTAP environment

Scheduler

The scheduling node (gateway) that runs the scheduler, typically on the search head, communicates with DCNs over port 8008 (default). If your environment uses port 8008 for another service, configure another port for communication between the DCN and the scheduling node. All data collection nodes do not have to communicate on the same port. You can configure the ports in the default stanza to implement the port change for all data collection nodes, or configure the port for each data collection node individually on a per stanza basis.

To set the port for the Hydra gateway, edit the configuration settings for the port on the scheduling node (usually implemented on the search head) in $SPLUNK_HOME/etc/apps/Splunk_TA_ontap/local/hydra_node.conf. See an example of the default setting for the app below.

[default]
gateway_port = 8008

The hydra gateway port, default value 8008, uses the SSL certs that Splunk Web uses. Splunk Enterprise generates these SSL certs by default, but you can override them in the web.conf file. The only information that travels machine-to-machine over the gateway port is hydra job assignment, configuration, and performance information. Hydra passes no credentials or session keys for the target environment though the gateway port. Credentials pass only through the storage/passwords endpoint on Splunkd on default port 8089.

You can add data collection nodes to the scheduler and configure worker processes on each during the installation of the app. Each time you access a node, the credentials for Splunk and the add-ons on that node are validated. Do this for each data collection node on an individual basis.


Check authentication and validation status of your ONTAP filers

In the Splunk Add-on for NetApp Data ONTAP connectivity and credential validation are checked for a filer, or for a set of filers, during the configuration of the app, only after you click Save in the Edit ONTAP Collection dialog or the Add ONTAP Collection dialog. If there is a change to your environment after you have installed the app and configured data collection, for example, if the password on a filer changes, that change is not automatically reflected in the Collection Configuration page. This change can prevent you from logging in to a filer and prevent data collection.

If you notice that you have stopped receiving data from a filer, go to the Collection Configuration page and click Refresh Validation to check if there are connectivity issues that the refresh action can identify for that filer.

After fixing the connectivity issues you can wait up to 30 minutes for the data to come in to the app as when a data collection node recognizes that it cannot connect to the filers, the worker processes limit that rate of attempts to login to the filer to once in a 30 minute period per filer.

You can also click Stop/Start scheduler to stop and restart data collection. This restarts data collection immediately from your ONTAP environment into Splunk.

Remember that if you add a new ONTAP filer as a target when the scheduler is running, you must stop and restart the scheduler to include the new filer as a data collection target. Refresh Validation does not update your Splunk environment.

Edit ONTAP Credentials

Delete a realm or change the credentials for a realm that you defined for a target asset (ONTAP server) or set of assets on the ONTAP Collection configuration dashboard.

Use caution when deleting credentials. The same credentials can be used by more than one consumer. When credentials are deleted and they are still used in other areas of your environment, then credential validation will fail for the consumers of those credentials.

Delete credentials that belong only to the Splunk Add-on for NetApp Data ONTAP, and only those that do not have an associated entry in the ONTAP Collection Configuration Page or an entry in the ta_ontap_collection_config.conf file.

To delete a realm

  1. Select a realm from the table. The Edit ONTAP Credential dialog is displayed.
  2. Click Delete Server to delete the credentials. This operation cannot be undone.
  3. A confirmation dialog is displayed.
  4. Click Delete Server to confirm your actions.

To change the credentials for a realm

  1. Select a realm from the table. The Edit ONTAP Credential dialog is displayed.
  2. Enter a new password in the Realm password text box.
  3. Click Save.

Edit data collection node settings

To edit the configuration of your data collection node:

  1. On the Collection Configuration dashboard, in the Data Collection Nodes panel, click on the node you want to modify.
  2. You can edit the properties for the node, then click Save to update the configuration.

Delete a data collection node

Deleting a data collection node unregisters it from your scheduler. It no longer processes data or forwards data to your Splunk indexer.

To remove a data collection node from the scheduler configuration:

  1. On the Collection Configuration dashboard, in the Data Collection Nodes panel, click on the node in the list, then click Delete node.
  2. Confirm that you want to delete the node.
  3. The node is removed from the list of nodes in the dashboard.

Edit ONTAP server settings

To edit filer settings:

  1. On the Collection Configuration dashboard, in the ONTAP collection configuration panel, click on the filer you want to modify.
  2. You can edit the properties for the filer, then click Save to update the configuration.

Delete a server

Deleting a server (filer) removes it from your Splunk environment. You will no longer collect data from this machine. When you add or remove a filer from your environment you must stop and restart the scheduler.

To delete a server:

  1. On the Collection Configuration dashboard, in the ONTAP Collection Configuration panel, select the server from the list of target machines. The Edit ONTAP Collection dialog is displayed.
  2. Click Delete Server.
  3. Confirm that you want to delete the filer, then click Save.
  4. The filer is removed as a data source and it is removed from the list of target machines in the dashboard.

Configure ONTAP servers

You can change the configuration settings of the ONTAP servers ( 7-mode or cluster mode) that you set up to work with the Splunk App for NetApp Data ONTAP. To do this, select the ONTAP server from the list of targets in the ONTAP Collection Configuration panel. The Edit ONTAP Collection dialog is displayed.

Configure performance category options

You can change the performance data collection options for your servers:

  1. On the ONTAP Collection Configuration dashboard, in the ONTAP Collection Configuration panel, select the filer you want to reconfigure from the list of available filers. You can also use the ONTAP Server search box to find the specific filer.
  2. To collect all performance data from the host, click "Collect All performance Categories".
  3. To reduce the set of categories from which you want to collect performance data, uncheck the box. A list of performance categories is displayed (Volume, Disk, LUN, Aggregate, Vfiler, Qtree, Quota, System). Select the the check boxes that define the data set you want to collect.
  4. Click Save to return to the dashboard.
  5. To validate that you are only collecting data from the performance categories you selected, from the app menu, select Settings, then App Data Volume. The App Data Volume dashboard displays a list of data types and source types for the data you are collecting over the last 24 hour period.

Configure realm based access

You can set a server or group of servers to have realm based credentials. The ONTAP Collection Configuration page lists all of the realms defined within the app context.

  1. In the Add ONTAP Collection dialog box, click Use Realm based Credentials.
  2. Enter a realm.
  3. Click Save.
Last modified on 13 September, 2024
Set up the Splunk Add-on for NetApp Data ONTAP to collect data from your ONTAP environment   Extracted Field Information

This documentation applies to the following versions of Splunk® Supported Add-ons: released


Was this topic useful?







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