<?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: Monitor ASA Firewall failover state using SNMP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4295341#M1078685</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/287680"&gt;@Sheraz.Salim&lt;/a&gt; You're welcome.&lt;/P&gt;
&lt;P&gt;Note that if you use FTD the management interfaces are similarly separately configured in an HA pair. However if you try to use the diagnostic interfaces they work more like normal routed dataplane interfaces. This is a shortcoming as of 6.7 - I am told 7.0 will remedy the situation.&lt;/P&gt;</description>
    <pubDate>Mon, 22 Feb 2021 14:57:07 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2021-02-22T14:57:07Z</dc:date>
    <item>
      <title>Monitor ASA Firewall failover state using SNMP</title>
      <link>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294145#M1078603</link>
      <description>&lt;P&gt;Team, I researched about this and couldn't find a straight forward answer for this. Is there a simple OID to poll which firewall hardware unit in a firewall failover pair is Active and which one is standby?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found OIDs to poll the state of the firewalls, but since the IP address from the Active transfers to the Standby during failover, there's no easy way for the NMS to know which unit it is.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Feb 2021 06:45:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294145#M1078603</guid>
      <dc:creator>ronit</dc:creator>
      <dc:date>2021-02-19T06:45:25Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor ASA Firewall failover state using SNMP</title>
      <link>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294166#M1078605</link>
      <description>HI Ronit,&lt;BR /&gt;&lt;BR /&gt;This will be helpful&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/security-documents/snmp-mibs-and-traps-on-the-asa-additional-information/ta-p/3116514" target="_blank"&gt;https://community.cisco.com/t5/security-documents/snmp-mibs-and-traps-on-the-asa-additional-information/ta-p/3116514&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Please look for OID cfwHardwareStatusValue&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards,&lt;BR /&gt;Dinesh Moudgil&lt;BR /&gt;&lt;BR /&gt;P.S.Please rate helpful posts.</description>
      <pubDate>Fri, 19 Feb 2021 07:33:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294166#M1078605</guid>
      <dc:creator>Dinesh Moudgil</dc:creator>
      <dc:date>2021-02-19T07:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor ASA Firewall failover state using SNMP</title>
      <link>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294168#M1078606</link>
      <description>&lt;P&gt;Hi Ronit,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This will be helpful&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/security-documents/snmp-mibs-and-traps-on-the-asa-additional-information/ta-p/3116514" target="_blank"&gt;https://community.cisco.com/t5/security-documents/snmp-mibs-and-traps-on-the-asa-additional-information/ta-p/3116514&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please look for OID cfwHardwareStatusValue&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks and Regards,&lt;BR /&gt;Dinesh Moudgil&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;P.S.Please rate helpful posts.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Feb 2021 07:33:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294168#M1078606</guid>
      <dc:creator>Dinesh Moudgil</dc:creator>
      <dc:date>2021-02-19T07:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor ASA Firewall failover state using SNMP</title>
      <link>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294172#M1078607</link>
      <description>&lt;P&gt;Thanks, but there's a problem with this approach. Let's assume Primary Unit has an IP of 192.168.1.1 and the Secondary Unit has an IP of 192.168.1.2.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the normal state, things are good. 192.168.1.1 reports Active, 192.168.1.2 reports Standby&lt;/P&gt;&lt;P&gt;When Unit-2 fails, things are good then, too -&amp;nbsp;192.168.1.1 reports Active, 192.168.1.2 doesn't report anything&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, when Unit-1 fails is the problem, because the IP 192.168.1.1 shifts to the secondary unit and 192.168.1.2 stops responding. Because of this, the NMS would still think that 192.168.1.1 (Which it thinks is the Primary unit) is active, which doesn't match reality.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Feb 2021 07:44:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294172#M1078607</guid>
      <dc:creator>ronit</dc:creator>
      <dc:date>2021-02-19T07:44:07Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor ASA Firewall failover state using SNMP</title>
      <link>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294181#M1078609</link>
      <description>&lt;P&gt;ASA management addresses can be uniquely assigned per member in an HA pair. They don't change when a failover event occurs (unlike how&amp;nbsp; the dataplane interfaces do).&lt;/P&gt;</description>
      <pubDate>Fri, 19 Feb 2021 08:12:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294181#M1078609</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2021-02-19T08:12:42Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor ASA Firewall failover state using SNMP</title>
      <link>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294688#M1078643</link>
      <description>&lt;P&gt;As friend suggest,&amp;nbsp;&lt;BR /&gt;Using the SNMP OID is solve issue,&amp;nbsp;&lt;/P&gt;&lt;P&gt;do you check management interface because as I read this interface also change from active to standby and hence you cannot use for SNMP.&lt;/P&gt;</description>
      <pubDate>Sat, 20 Feb 2021 12:57:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4294688#M1078643</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2021-02-20T12:57:11Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor ASA Firewall failover state using SNMP</title>
      <link>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4295170#M1078678</link>
      <description>&lt;P&gt;Nice one &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt; I did not know that. learn something new today.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/779369"&gt;@ronit&lt;/a&gt; you question was very good.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2021 08:57:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4295170#M1078678</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2021-02-22T08:57:35Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor ASA Firewall failover state using SNMP</title>
      <link>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4295341#M1078685</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/287680"&gt;@Sheraz.Salim&lt;/a&gt; You're welcome.&lt;/P&gt;
&lt;P&gt;Note that if you use FTD the management interfaces are similarly separately configured in an HA pair. However if you try to use the diagnostic interfaces they work more like normal routed dataplane interfaces. This is a shortcoming as of 6.7 - I am told 7.0 will remedy the situation.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2021 14:57:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4295341#M1078685</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2021-02-22T14:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor ASA Firewall failover state using SNMP</title>
      <link>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4704689#M1094310</link>
      <description>&lt;P&gt;I tried configuring uniquely assigned IPs on our FPR1120s running ASA 9.14, however, even without the "standby" keyword, the interface config is copied over to the secondary ASA. Any idea what I could be doing wrong?&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2022 06:29:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-asa-firewall-failover-state-using-snmp/m-p/4704689#M1094310</guid>
      <dc:creator>ronit</dc:creator>
      <dc:date>2022-10-18T06:29:32Z</dc:date>
    </item>
  </channel>
</rss>

