Upgrade the Splunk Add-on for Cisco ISE¶
Upgrade from version 5.0.0 to version 5.0.1¶
Upgrade from Splunk Add-on for Cisco ISE version 5.0.0 to version 5.0.1 requires no additional configuration steps.
After upgrading, review saved searches, reports, and dashboards that filter
on user_type. Version 5.0.1 maps user_type directly from the raw Cisco
ISE UserType field. Events without a raw UserType field no longer receive
the synthetic user_type values that were assigned by earlier versions.
For multiline Cisco ISE records collected through direct network inputs,
file-monitor inputs, or universal forwarders, set the cisco:ise:syslog
sourcetype at input time and install the add-on on the Splunk parsing tier or
forwarder that processes the raw stream. A generic syslog sourcetype can
split multiline records before automatic Cisco ISE sourcetype detection
occurs. Multiline records sent by SC4S over HEC are not covered by this
configuration and require upstream SC4S support.
Upgrade from version 4.2.0 to version 5.0.0¶
Upgrade from Splunk Add-on for Cisco ISE version 4.2.0 to v5.0.0 requires no additional steps to be performed.
Upgrade from version 4.1.0 to version 4.2.0¶
Upgrade from Splunk Add-on for Cisco ISE version 4.1.0 to version 4.2.0 requires no additional steps to be performed.
Upgrade from version 4.0.0 to version 4.1.0¶
Upgrade from Splunk Add-on for Cisco ISE version 4.0.0 to version 4.1.0 requires no additional steps to be performed.
Upgrade an indexer cluster from Splunk Add-on for Cisco ISE version 3.0.0¶
- On the cluster master of your indexer cluster Splunk platform
deployment, navigate to
$SPLUNK_HOME/etc/master-apps/Splunk_TA_cisco-ise/local/. -
Open
props.confand edit thecisco:isestanza to remove the following line:DATETIME_CONFIG = /etc/slave-apps/Splunk_TA_cisco-ise/default/datetime_udp.xml -
Edit the
cisco:ise:syslogstanza to remove the following line:DATETIME_CONFIG = /etc/slave-apps/Splunk_TA_cisco-ise/default/datetime_udp.xml -
Save your changes.
- Push the configurations to your peer nodes.