<?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 I'm not sure, but your ASDM in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asdm-filter/m-p/2811484#M160234</link>
    <description>&lt;P&gt;I'm not sure, but your ASDM is a major version behind. &amp;nbsp;The current version is 7.x.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;If you have a Cisco maintenance contract, such as a SmartNet, then you can get a newer ASDM for the ASA.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have always found the ASDM log filtering a little tricky to get to work for anything other than simple filters.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Jan 2016 22:18:03 GMT</pubDate>
    <dc:creator>Philip D'Ath</dc:creator>
    <dc:date>2016-01-28T22:18:03Z</dc:date>
    <item>
      <title>ASDM filter</title>
      <link>https://community.cisco.com/t5/network-security/asdm-filter/m-p/2811483#M160233</link>
      <description>&lt;P&gt;Here's a question,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;When I try to find a rule on the ASDM that has multiple words in the name, nothing&amp;nbsp;found if I use&amp;nbsp;any word other than the first word.&amp;nbsp;For example, if I'm looking for a policy that may have DNS in the source or destination field, and the name is actually Servers_DNS, if I click find and enter DNS in the source or destination field then nothing is found even with the parameter set to contains.&amp;nbsp; But the policy is actually there.&amp;nbsp; Any idea why this is or a work around for it?&amp;nbsp; We are on ASDM 6.4&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Corey&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:12:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-filter/m-p/2811483#M160233</guid>
      <dc:creator>corey.burden</dc:creator>
      <dc:date>2019-03-12T07:12:48Z</dc:date>
    </item>
    <item>
      <title>I'm not sure, but your ASDM</title>
      <link>https://community.cisco.com/t5/network-security/asdm-filter/m-p/2811484#M160234</link>
      <description>&lt;P&gt;I'm not sure, but your ASDM is a major version behind. &amp;nbsp;The current version is 7.x.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;If you have a Cisco maintenance contract, such as a SmartNet, then you can get a newer ASDM for the ASA.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have always found the ASDM log filtering a little tricky to get to work for anything other than simple filters.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 22:18:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-filter/m-p/2811484#M160234</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-01-28T22:18:03Z</dc:date>
    </item>
    <item>
      <title>Well, I at least upgraded the</title>
      <link>https://community.cisco.com/t5/network-security/asdm-filter/m-p/2811485#M160235</link>
      <description>&lt;P&gt;Well, I at least upgraded the version!&amp;nbsp; But the problem still remained.&amp;nbsp; However, I think I found a solution.&amp;nbsp; I used an * wildcard in front of the name and that found policies that had the specified word contained in the name.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Feb 2016 14:22:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-filter/m-p/2811485#M160235</guid>
      <dc:creator>corey.burden</dc:creator>
      <dc:date>2016-02-01T14:22:09Z</dc:date>
    </item>
  </channel>
</rss>

