Storage Module troubleshooting

Permissions

Verify that Splunk Add-on for NetApp Data ONTAP and the Splunk Add-on for EMC VNX have global permissions. Learn about adding navigation to a Splunk app.

Verify services are enabled

1. Navigate to the version of the ITSI that is installed on your Splunk platform deployment.
2. Click Configuration > Services.
3. Verify that the storage module services you created are enabled.

Verify that storage module entities are imported successfully and mapped with storage module services

1. Navigate to the version of the ITSI that is installed on your Splunk platform deployment.
2. Click Configuration > Services.
3. Select the service you want to check.
4. Go to the "Entities" tab and verify that entities are being listed.
5. If entities are not being listed, remove each rule to check which one is not being satisfied.

Add-ons are global but ITSI KPIs and Dashboards are not populating

If your add-ons are global but ITSI KPIs and dashboards are not populating:

1. Navigate to Settings > Roles.
2. Click itoa_admin and navigate to Inheritance to verify that itoa_admin has splunk_ontap_admin and splunk_ontap_user roles assigned to it. The itoa_admin role is the admin role for Splunk IT Service Intelligence. It should have access to indexes of apps that you want to monitor in ITSI.
3. Check that the index specified during configuration of the Splunk Add-on for EMCVNX is set as Indexes searched by default for the itoa_admin user.
4. Click Save

Check Collection Configuration of Splunk Add-on for NetApp Data ONTAP

1. Navigate to the version of the Splunk Add-on for NetApp Data ONTAP that is installed on your Splunk platform deployment.
2. On the ONTAP Collection Configuration page, verify that the collection configurations are correct.

Change collection intervals

Change collection intervals for the Splunk Add-on for NetApp Data ONTAP

Adjust your deployment's data collection interval settings. This reduces the load on your Data Collection Nodes (DCNs) and helps avoid data gaps in your Storage Module KPIs.

1. Create a ta_ontap_collection.conf file in $SPLUNK_HOME/etc/apps/Splunk_TA_ontap/local/, (using the ta_ontap_collection.conf in $SPLUNK_HOME/etc/apps/Splunk_TA_ontap/default/ as reference) if it does not already exist.
2. Navigate to $SPLUNK_HOME\etc\apps\Splunk_TA_ontap\local\ and open the ta_ontap_collection.conf file.
3. Make the following changes:
   1. Change megaperf_interval and megaperf_expiration from the 300 second default to a larger number (maximum 900 seconds). Maximum limit that can be set here can not exceed 900 seconds because Storage Module KPIs populate for performance data of the last 15 minutes (900 sec). If you set collection configuration time greater than 900 then KPIs will not populate. Keep the value that you assign to megaperf_expiration 5 to 10 seconds lower than the value you assign to the megaperf_interval.
   2. Save your changes and exit.
   3. Restart your Splunk platform instance.
4. Navigate to $SPLUNK_HOME\etc\apps\Splunk_TA_ontap\local\ and open the ta_ontap_collection.conf file.
5. Change the time interval for inventory data by making the following changes:
   1. Change megainv_interval and megainv_expiration from the 600 second default to a larger number (maximum 1200 seconds). Keep the value that you assign to megainv_expiration 5 to 10 seconds lower than the value you assign to the megainv_interval .
   2. Save your changes and exit.
   3. Restart your Splunk platform instance.

See the Configure inputs section of the Splunk Add-on for NetApp Data ONTAP for more information.

Change collection intervals of Splunk Add-on for EMC VNX

Adjust your deployment's data collection intervals. This reduces the load on your Data Collection Nodes (DCNs) and helps avoid data gaps in your Storage Module KPIs.

1. Create a ta_vnx_collection.conf file in $SPLUNK_HOME/etc/apps/Splunk_TA_emc-vnx/local/, (using the ta_vnx_collection.conf in $SPLUNK_HOME/etc/apps/Splunk_TA_emc-vnx/default/ as reference) if it does not already exist.
2. Navigate to $SPLUNK_HOME\etc\apps\Splunk_TA_emc-vnx\local\ and open the ta_vnx_collection.conf file.
3. Make the following changes to the time interval for your performance job.
   1. Open the ta_vnx_collection.conf file.
   2. Change vnx_file_sys_performance_interval, vnx_file_nfs_performance_interval , vnx_file_cifs_performance_interval, and vnx_block_performance_interval from the 120 second default to a larger number (maximum 900 seconds). Maximum limit that can be set here can not exceed 900 seconds because storage module KPIs populate for last 15 minutes (900 sec). If you set the collection configuration time greater than 900 seconds, then KPIs will not populate.
   3. Save your changes and exit.
   4. Restart your Splunk platform instance.

See the Configure the collection interval for the Splunk Add-on for EMC VNX for more information.

Learn more

See the troubleshooting section of the Splunk Add-on for NetApp Data ONTAP.

See the troubleshooting section of the Splunk Add-on for EMC VNX.