<?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: Unable to configure ISE to receive SNMP traps in DevNet General Discussions</title>
    <link>https://community.cisco.com/t5/devnet-general-discussions/unable-to-configure-ise-to-receive-snmp-traps/m-p/3461099#M196</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Apparently I had to check the SNMP trap flag in administration-&amp;gt;system-&amp;gt;deployment-&amp;gt;profiling configuration. I definitely went over a large number of configuration docs and didn't come across this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, while I don't get the ICMP port unreachable anymore I don't see any effect of the traps on ISE. No new information is added to the UI. Is there a simple trap that can show me that the entire SNMP traps mechanism works?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Apr 2018 15:47:23 GMT</pubDate>
    <dc:creator>orp</dc:creator>
    <dc:date>2018-04-03T15:47:23Z</dc:date>
    <item>
      <title>Unable to configure ISE to receive SNMP traps</title>
      <link>https://community.cisco.com/t5/devnet-general-discussions/unable-to-configure-ise-to-receive-snmp-traps/m-p/3461098#M195</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, I'm trying to have ISE (2.3) receive info from my switches by receiving SNMP traps. I've configured the switches to send the traps to ISE, and I even see them in Wireshark, but I get an ICMP port unreachable for each one (port 162). I've followed several configuration guides but still no success.&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 10:57:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-general-discussions/unable-to-configure-ise-to-receive-snmp-traps/m-p/3461098#M195</guid>
      <dc:creator>orp</dc:creator>
      <dc:date>2019-03-01T10:57:54Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to configure ISE to receive SNMP traps</title>
      <link>https://community.cisco.com/t5/devnet-general-discussions/unable-to-configure-ise-to-receive-snmp-traps/m-p/3461099#M196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Apparently I had to check the SNMP trap flag in administration-&amp;gt;system-&amp;gt;deployment-&amp;gt;profiling configuration. I definitely went over a large number of configuration docs and didn't come across this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, while I don't get the ICMP port unreachable anymore I don't see any effect of the traps on ISE. No new information is added to the UI. Is there a simple trap that can show me that the entire SNMP traps mechanism works?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2018 15:47:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-general-discussions/unable-to-configure-ise-to-receive-snmp-traps/m-p/3461099#M196</guid>
      <dc:creator>orp</dc:creator>
      <dc:date>2018-04-03T15:47:23Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to configure ISE to receive SNMP traps</title>
      <link>https://community.cisco.com/t5/devnet-general-discussions/unable-to-configure-ise-to-receive-snmp-traps/m-p/3461100#M197</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just upgraded to ISE 2.4 and it seems to work much better. I get numerous devices discovered and much more information obtained from each.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Apr 2018 06:21:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-general-discussions/unable-to-configure-ise-to-receive-snmp-traps/m-p/3461100#M197</guid>
      <dc:creator>orp</dc:creator>
      <dc:date>2018-04-05T06:21:19Z</dc:date>
    </item>
  </channel>
</rss>

