<?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 snmpv3 with Active Failover in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/snmpv3-with-active-failover/m-p/1949516#M457497</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 07 Apr 2012 21:09:36 GMT</pubDate>
    <dc:creator>Brian Evan</dc:creator>
    <dc:date>2012-04-07T21:09:36Z</dc:date>
    <item>
      <title>snmpv3 with Active Failover</title>
      <link>https://community.cisco.com/t5/network-security/snmpv3-with-active-failover/m-p/1949514#M457493</link>
      <description>&lt;P&gt;What I am attempting to do is setup snmpv3 on two failover 5510's .&lt;/P&gt;&lt;P&gt;The problem I am running into, the snmp management software rejects one of the devices as it sees it as having a duplicate engine ID since the two devices share the same config.&amp;nbsp; Has anyone dealt with this issue before?&amp;nbsp; Would like to know how this would work in an active/active setup being able to poll both devices.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:49:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/snmpv3-with-active-failover/m-p/1949514#M457493</guid>
      <dc:creator>Brian Evan</dc:creator>
      <dc:date>2019-03-11T22:49:44Z</dc:date>
    </item>
    <item>
      <title>snmpv3 with Active Failover</title>
      <link>https://community.cisco.com/t5/network-security/snmpv3-with-active-failover/m-p/1949515#M457495</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Brian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, this is by design in the current ASA failover and SNMP implementation. There is an enhancement request filed to change this behavior but it has not been implemented yet:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSCtl88556 - ASA5520 failover pair has duplicate snmp v3 engine id&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Apr 2012 16:01:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/snmpv3-with-active-failover/m-p/1949515#M457495</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2012-04-07T16:01:30Z</dc:date>
    </item>
    <item>
      <title>snmpv3 with Active Failover</title>
      <link>https://community.cisco.com/t5/network-security/snmpv3-with-active-failover/m-p/1949516#M457497</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Apr 2012 21:09:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/snmpv3-with-active-failover/m-p/1949516#M457497</guid>
      <dc:creator>Brian Evan</dc:creator>
      <dc:date>2012-04-07T21:09:36Z</dc:date>
    </item>
  </channel>
</rss>

