Upgrade the Splunk Add-on for NetApp Data ONTAP to v3.0.1

Follow these steps when upgrading Splunk Add-on for NetApp Data ONTAP.

Step 1: Download the files from Splunkbase

Download the Splunk Add-on for NetApp Data ONTAP v3.0.1 from Splunkbase to a location in your environment.

Step 2: Upgrade the scheduler

Make sure splunk_ontap_admin role has admin_all_objects capability before upgrading the scheduler.

1. Navigate to the ONTAP Collection Configuration page of the Netapp add-on and click Stop Scheduler.
2. Stop Splunk on the scheduler instance.
3. Extract the contents of the Splunk Add-on for NetApp Data ONTAP to the $SPLUNK_HOME/etc/apps directory. This overwrites the previously installed add-on packages.
4. Go to $PLUNK_HOME/etc/apps and remove the following directories:
   1. SA-ONTAPIndex
   2. TA-ONTAP-FieldExtractions
   3. SA-VMNetAppUtils
5. If present, remove /appserver folder from SA-Hydra.
6. If present, remove the /appserver/modules folder from Splunk_TA_ontap.
7. Sync the $SPLUNK_HOME/etc/apps/Splunk_TA_ontap/local /ta_ontap_collection.conf by using saved search or without using saved search:

With saved search:

1. Restart the Splunk platform on the scheduler instance.
2. Go to Settings>Searches, Reports, and Alerts.
3. Select Splunk_TA_ontap from the dropdown of apps
4. Search for "Conf Synchronization" Saved search and click on "Run".
5. Check for the success message for all the stanzas of ta_ontap_collection.conf.

Without using saved search:

1. Navigate to $SPLUNK_HOME/etc/apps/Splunk_TA_ontap/local /ta_ontap_collection.conf. Find the property named ##"perf_whitelist" in all the stanzas and replace it with perf_includelist.

Step 3: Upgrade the data collection node

1. Stop the Splunk on the DCN machine.
2. Extract the contents of the Splunk Add-on for NetApp Data ONTAP to $SPLUNK_HOME/etc/apps directory. This overwrites the previously installed add-on packages.
3. Go to $PLUNK_HOME/etc/apps and remove the following directories:
   1. SA-ONTAPIndex
   2. TA-ONTAP-FieldExtractions
   3. SA-VMNetAppUtils
4. If present, remove /appserver folder from SA-Hydra.
5. If present, remove the /appserver/modules folder from Splunk_TA_ontap.

(Optional) Step 4: Upgrade the indexer

1. Enable maintenance mode on the cluster master node.
2. Navigate to the /apps folder for your deployment. For a non-indexer cluster deployment, navigate to $SPLUNK_HOME/etc/apps. For the indexer clustering deployments, navigate to SPLUNK_HOME/etc/master-apps.
3. Overwrite SA-ONTAPIndex with the new version.
4. If you set up an indexer cluster, push the configuration bundle from the cluster master node.

Step 5: Upgrade the search head

1. Stop the Splunk on the machine.
2. Navigate to the /apps folder for your deployment. For non-search head cluster deployments, navigate to $SPLUNK_HOME/etc/apps. For search head clustering deployments, navigate to $SPLUNK_HOME/etc/shcluster/apps/.
3. Rename the package SA-VMNetAppUtils to "SA-VMNetAppUtils-backup".
4. Upgrade the add-on. This overwrites SA-Hydra and TA-ONTAP-FieldExtractions with the new version.
5. Go to /apps/SA-VMNetAppUtils-backup/ and copy the local directory to the /apps/SA-VMNetAppUtils/ directory.
6. Delete the SA-VMNetAppUtils-backup directory from /apps.
7. If present, remove the /appserver folder from SA-Hydra.
8. If you set up a search head cluster, push the app bundle from the deployer. The deployer restarts all the search head cluster members after the upgrade is applied. If the deployer does not restart the search head cluster members, perform a rolling restart.

Step 6: Start the scheduler

1. Start the Splunk on the DCN machine.
2. Start the Splunk on the scheduler machine.
3. Navigate to the ONTAP Collection Configuration page of the Netapp add-on.
4. Click Start Scheduler to start data collection.