<?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: ADE-OS issues with SNMPv2 and SNMPv3 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ade-os-issues-with-snmpv2-and-snmpv3/m-p/3780376#M486286</link>
    <description>&lt;P&gt;Hi Timothy,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This isn't about an enhancement, it's about previous functionality which no longer works. SNMP has been baked and working within ADE-OS for&amp;nbsp;over a decade (i.e. since at least the days of Application Networking Manager).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If SNMP&amp;nbsp;isn't designed to work for ISE&amp;nbsp;then it shouldn't be configurable within CLI to begin with. Or at the very least update the CLI configuration guide to state that SNMP is not supported:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/cli_guide/b_ise_CLIReferenceGuide_24/b_ise_CLIReferenceGuide_24_chapter_011.html#wp4278751266" target="_self"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/cli_guide/b_ise_CLIReferenceGuide_24/b_ise_CLIReferenceGuide_24_chapter_011.html#wp4278751266&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 15 Jan 2019 17:27:07 GMT</pubDate>
    <dc:creator>Nadav</dc:creator>
    <dc:date>2019-01-15T17:27:07Z</dc:date>
    <item>
      <title>ADE-OS issues with SNMPv2 and SNMPv3</title>
      <link>https://community.cisco.com/t5/network-access-control/ade-os-issues-with-snmpv2-and-snmpv3/m-p/3780164#M486271</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm seeing issues with SNMP polling and traps for both SNMPv2 and SNMPv3. I've seen these issues on both ISE 2.4 P4, and ISE 2.4 P5.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Issues for v2:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1) Sends trap when a process is running, doesn't send a trap when a process is stopped.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2) Doesn't send trap on reboot or shutdown.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Issues with v3:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1) No traps for process running or stopped&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2) No traps for reboot or shutdown&lt;/P&gt;
&lt;P&gt;3) Sometimes doesn't work at all because the OS stores two v3 usernames. This is confirmed by the command "show snmp user".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There are long-open issues such as&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc80795/?rfs=iqvred" target="_self"&gt;CSCvc80795&lt;/A&gt;&amp;nbsp;which are a big vague, but what I'm seeing as in existing issue under the latest GA builds for all forms of SNMP.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can someone from Cisco please address the existence of these caveats and whether or not they are being fixed in upcoming versions?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jan 2019 14:46:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ade-os-issues-with-snmpv2-and-snmpv3/m-p/3780164#M486271</guid>
      <dc:creator>Nadav</dc:creator>
      <dc:date>2019-01-15T14:46:33Z</dc:date>
    </item>
    <item>
      <title>Re: ADE-OS issues with SNMPv2 and SNMPv3</title>
      <link>https://community.cisco.com/t5/network-access-control/ade-os-issues-with-snmpv2-and-snmpv3/m-p/3780190#M486277</link>
      <description>&lt;P&gt;We do have enhancement requests such as the one you referenced already submitted.&amp;nbsp; The challenge is determining when they will be added to a future release and if they have the potential to be added, there is a possibility they may not make it in a release for one reason or another.&amp;nbsp; I recommend reaching out to your account team to set up a meeting for a roadmap discussion as we are unable to post anything related to futures in this forum.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;-Tim&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jan 2019 15:07:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ade-os-issues-with-snmpv2-and-snmpv3/m-p/3780190#M486277</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2019-01-15T15:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: ADE-OS issues with SNMPv2 and SNMPv3</title>
      <link>https://community.cisco.com/t5/network-access-control/ade-os-issues-with-snmpv2-and-snmpv3/m-p/3780376#M486286</link>
      <description>&lt;P&gt;Hi Timothy,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This isn't about an enhancement, it's about previous functionality which no longer works. SNMP has been baked and working within ADE-OS for&amp;nbsp;over a decade (i.e. since at least the days of Application Networking Manager).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If SNMP&amp;nbsp;isn't designed to work for ISE&amp;nbsp;then it shouldn't be configurable within CLI to begin with. Or at the very least update the CLI configuration guide to state that SNMP is not supported:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/cli_guide/b_ise_CLIReferenceGuide_24/b_ise_CLIReferenceGuide_24_chapter_011.html#wp4278751266" target="_self"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/cli_guide/b_ise_CLIReferenceGuide_24/b_ise_CLIReferenceGuide_24_chapter_011.html#wp4278751266&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jan 2019 17:27:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ade-os-issues-with-snmpv2-and-snmpv3/m-p/3780376#M486286</guid>
      <dc:creator>Nadav</dc:creator>
      <dc:date>2019-01-15T17:27:07Z</dc:date>
    </item>
  </channel>
</rss>

