<?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 Re: Failure notification using SNMP traps in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/failure-notification-using-snmp-traps/m-p/3588663#M538967</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Utkarsh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is not a supported feature.&amp;nbsp; A workaround would be to send syslog messsages that would alert of authentication failures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 May 2016 15:53:12 GMT</pubDate>
    <dc:creator>Timothy Abbott</dc:creator>
    <dc:date>2016-05-04T15:53:12Z</dc:date>
    <item>
      <title>Failure notification using SNMP traps</title>
      <link>https://community.cisco.com/t5/network-access-control/failure-notification-using-snmp-traps/m-p/3588662#M538966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a distributed environment with multiple PSNs spreading across multiple location.&lt;/P&gt;&lt;P&gt;We want to optimize ISE operations and want to explore if there is any option to send SNMP traps for authentication failures.&lt;/P&gt;&lt;P&gt;Is this feature supported ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 May 2016 07:22:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/failure-notification-using-snmp-traps/m-p/3588662#M538966</guid>
      <dc:creator>umahar</dc:creator>
      <dc:date>2016-05-04T07:22:05Z</dc:date>
    </item>
    <item>
      <title>Re: Failure notification using SNMP traps</title>
      <link>https://community.cisco.com/t5/network-access-control/failure-notification-using-snmp-traps/m-p/3588663#M538967</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Utkarsh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is not a supported feature.&amp;nbsp; A workaround would be to send syslog messsages that would alert of authentication failures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 May 2016 15:53:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/failure-notification-using-snmp-traps/m-p/3588663#M538967</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2016-05-04T15:53:12Z</dc:date>
    </item>
    <item>
      <title>Re: Failure notification using SNMP traps</title>
      <link>https://community.cisco.com/t5/network-access-control/failure-notification-using-snmp-traps/m-p/3588664#M538968</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It might be possible with a product that consumes syslog to be able to filter out certain things and report on them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example Splunk could consume MNT data&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 May 2016 17:39:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/failure-notification-using-snmp-traps/m-p/3588664#M538968</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2016-05-04T17:39:23Z</dc:date>
    </item>
  </channel>
</rss>

