Upgrade from Splunk Add-on for VMware Metrics version 4.0.0 or 4.1.0 to version 4.2.0

Perform the following steps to upgrade from version 4.0.0 or 4.1.0 of the Splunk Add-on for VMware Metrics to version 4.2.0.

Upgrade your DCS

You can upgrade your DCS manually or using an upgrade script.

Upgrade your DCS using an upgrade script

1. Download and unzip the following upgrade script and put it on the scheduler machine: Upgade_from_VMware_Metric_TA_400_410_to_420.zip
2. Stop the scheduler from the Collection Configuration page of Splunk Add-on for VMware Metrics.
3. Stop Splunk on the Scheduler instance.
4. Extract the contents of the Splunk Add-on for VMware Metrics version 4.2.0 to the $SPLUNK_HOME/etc/apps directory.
5. Go to $SPLUNK_HOME/etc/apps and delete the following packages:
   • Splunk_TA_vcenter
   • Splunk_TA_esxilogs
   • SA-VMWIndex-inframon
6. Run the upgrade script using Python. Use the following command to run the script:

   $SPLUNK_HOME/bin/splunk cmd python upgrade_script_metric_TA.py
   

   You'll see a message saying that the add-on upgraded successfully. In case of errors, refer to the upgrade_metric_TA_from_410_to_420.log file present in $SPLUNK_HOME/var/log/splunk directory.

Manually upgrade your DCS

1. Stop the scheduler from the Collection Configuration page of Splunk Add-on for VMware Metrics.
2. Stop your Splunk instance.
3. Extract the contents of the Splunk Add-on for VMware Metrics to the $SPLUNK_HOME/etc/apps directory.
4. Go to the Splunk_TA_vmware_inframon/local directory and open the inframon_ta_vmware_template.conf file, if present. From each stanza, remove the following parameters and their respective values:

   host_perf_fields
   vm_perf_fields
   cluster_perf_fields
   

   You can filter the collection of performance metrics for Host/VM entities using the allowlist and denylist parameters present in the inframon_ta_vmware_template.conf file. The parameters host_perf_fields, vm_perf_fields and cluster_perf_fields are not supported in theinframon_ta_vmware_template.conf file. For more information, see Configure Metrics Allowlist/Denylist to filter performance data.

5. Replace the existing parameters in the file inframon_ta_vmware_collection.conf with the new parameter names at $SPLUNK_HOME/etc/apps/Splunk_TA_vmware_inframon/local per the following table in all the stanzas, if present.

   Parameter name in version 4.1.0	New parameter in version 4.2.0
   managed_host_whitelist	managed_host_includelist
   managed_host_blacklist	managed_host_excludelist
   vm_instance_whitelist	vm_instance_allowlist
   vm_instance_blacklist	vm_instance_denylist
   host_instance_whitelist	host_instance_allowlist
   host_instance_blacklist	host_instance_denylist
   cluster_instance_whitelist	cluster_instance_allowlist
   cluster_instance_blacklist	cluster_instance_denylist
   perf_entity_blacklist	perf_entity_denylist

6. Go to $SPLUNK_HOME/etc/apps and delete the following packages:
   • Splunk_TA_vcenter
   • Splunk_TA_esxilogs
   • SA-VMWIndex-inframon

Upgrade your DCN

1. Stop your Splunk instance.
2. Extract the contents of the Splunk Add-on for VMware Metrics to the $SPLUNK_HOME/etc/apps directory.
3. Go to $SPLUNK_HOME/etc/apps and delete the following packages:
   • SA-VMWIndex-inframon
   • Splunk_TA_vcenter (if forwarding vCenter logs directly to the indexer)
   • Splunk_TA_esxilogs (if forwarding ESXi logs directly to the indexer)

Upgrade your indexer

1. Stop the indexer.
2. Extract the contents of the Splunk Add-on for VMware Metrics to the $SPLUNK_HOME/etc/apps directory.
3. Go to $SPLUNK_HOME/etc/apps and delete the following packages:
   • Splunk_TA_vmware_inframon
   • SA-Hydra-inframon
   • Splunk_TA_vcenter (if forwarding vCenter logs directly to the DCN)
   • Splunk_TA_esxilogs (if forwarding ESXi logs directly to the DCN)

Start Splunk

1. Start Splunk on the DCN, scheduler, and indexer instances after upgrading them.
2. Start the scheduler from the Collection Configuration page of Splunk Add-on for VMware Metrics on the scheduler machine.