<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic CISCO ASA add on is not extracting fields in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/CISCO-ASA-add-on-is-not-extracting-fields/m-p/447653#M95286</link>
    <description>&lt;P&gt;We recently upgraded the environment from 6.5 to 7.2 and ever since there is an upgradation in the environment we see that the rule fields are not getting extracted properly for Cisco message id 106100 but it is getting extracted for cisco message id 106123. We have defined the props and transforms still not able to extract the rule field for message id 106100.  The rule field should be extracted by default but I see that some of the fields are not getting extracted by default but we need to extract it manually.&lt;/P&gt;</description>
    <pubDate>Mon, 06 May 2019 06:15:53 GMT</pubDate>
    <dc:creator>swmishra_splunk</dc:creator>
    <dc:date>2019-05-06T06:15:53Z</dc:date>
    <item>
      <title>CISCO ASA add on is not extracting fields</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CISCO-ASA-add-on-is-not-extracting-fields/m-p/447653#M95286</link>
      <description>&lt;P&gt;We recently upgraded the environment from 6.5 to 7.2 and ever since there is an upgradation in the environment we see that the rule fields are not getting extracted properly for Cisco message id 106100 but it is getting extracted for cisco message id 106123. We have defined the props and transforms still not able to extract the rule field for message id 106100.  The rule field should be extracted by default but I see that some of the fields are not getting extracted by default but we need to extract it manually.&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2019 06:15:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CISCO-ASA-add-on-is-not-extracting-fields/m-p/447653#M95286</guid>
      <dc:creator>swmishra_splunk</dc:creator>
      <dc:date>2019-05-06T06:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: CISCO ASA add on is not extracting fields</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CISCO-ASA-add-on-is-not-extracting-fields/m-p/447654#M95287</link>
      <description>&lt;P&gt;The is an observed behavior in Splunk 7.x versions, the FIELDALIAS overwrites the null value from the source field to the destination field and is having the values in it, So the final result is null value in the Destination field and because of which the baheviour change the rule field is not getting extracted. &lt;/P&gt;

&lt;P&gt;So you need to makes these changes in the props.conf &lt;BR /&gt;
Comment below in the $plunkhome/etc/apps/Spunk_TA_cisco-asa/default/props.conf&lt;BR /&gt;
FIELDALIAS-fwsm_acl_for_rule= acl as rule(in cisco:fwsm stanza)&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:21:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CISCO-ASA-add-on-is-not-extracting-fields/m-p/447654#M95287</guid>
      <dc:creator>saramamurthy_sp</dc:creator>
      <dc:date>2020-09-30T00:21:14Z</dc:date>
    </item>
  </channel>
</rss>

