<?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: Active/active failover in FWSM - silly question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/active-active-failover-in-fwsm-silly-question/m-p/698022#M1029493</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you, Jim&lt;/P&gt;&lt;P&gt;So, the active/active configuration means that each firewall can be primary for one context, and secondary for another context. It's just an active/standby config, but the primary and secondary roles can be allocated to firewalls per context. &lt;/P&gt;&lt;P&gt;I expected a different behavior, the active/active designation seemed to indicate that both firewalls can process traffic for the same context at the same time. &lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Cristian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Jan 2007 13:22:42 GMT</pubDate>
    <dc:creator>CRISTIAN LACATUS</dc:creator>
    <dc:date>2007-01-10T13:22:42Z</dc:date>
    <item>
      <title>Active/active failover in FWSM - silly question</title>
      <link>https://community.cisco.com/t5/network-security/active-active-failover-in-fwsm-silly-question/m-p/698020#M1029491</link>
      <description>&lt;P&gt;Hello &lt;/P&gt;&lt;P&gt;I have two 6500 switches, each with a FWSM running OS version 3.1(4). &lt;/P&gt;&lt;P&gt;I configured active/standby failover, followed by active/active failover. The configs for both types of failover look very similar. The only additions for active/active seem to be&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;! context system &lt;/P&gt;&lt;P&gt;failover group 1&lt;/P&gt;&lt;P&gt; primary&lt;/P&gt;&lt;P&gt;admin-context admin&lt;/P&gt;&lt;P&gt;context admin&lt;/P&gt;&lt;P&gt;  join-failover-group 1&lt;/P&gt;&lt;P&gt;context abc&lt;/P&gt;&lt;P&gt;  join-failover-group 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this all? Results displayed by the "show failover" command also look very similar. There is nothing to indicate an active/active configuration or active/standby. Is there a simple way to be 100% sure what type of failover is configured?&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Cristian&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;File with "show failover" results as attachment&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 09:16:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/active-active-failover-in-fwsm-silly-question/m-p/698020#M1029491</guid>
      <dc:creator>CRISTIAN LACATUS</dc:creator>
      <dc:date>2019-03-11T09:16:49Z</dc:date>
    </item>
    <item>
      <title>Re: Active/active failover in FWSM - silly question</title>
      <link>https://community.cisco.com/t5/network-security/active-active-failover-in-fwsm-silly-question/m-p/698021#M1029492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need to configure a second group which the secondary fwsm will be a primary.&lt;/P&gt;&lt;P&gt;#blade 1&lt;/P&gt;&lt;P&gt;Failover group 1 &lt;/P&gt;&lt;P&gt;failover group 2&lt;/P&gt;&lt;P&gt;secondary&lt;/P&gt;&lt;P&gt;#blade 2&lt;/P&gt;&lt;P&gt;failover group 2 &lt;/P&gt;&lt;P&gt;failover group 1 &lt;/P&gt;&lt;P&gt;secondary&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#sho failover&lt;/P&gt;&lt;P&gt;Failover On&lt;/P&gt;&lt;P&gt;Failover unit Secondary&lt;/P&gt;&lt;P&gt;Failover LAN Interface: FAILOVER Management0/0 (up) Unit Poll frequency 1 seconds, holdtime 15 seconds Interface Poll frequency 5 seconds, holdtime 25 seconds Interface Policy 1 Monitored Interfaces 3 of 250 maximum&lt;/P&gt;&lt;P&gt;Version: Ours 7.2(2), Mate 7.2(2)&lt;/P&gt;&lt;P&gt;Group 1 last failover at: 06:49:56 EST Jan 8 2007 Group 2 last failover at: 06:49:56 EST Jan 8 2007&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  This host:    Secondary&lt;/P&gt;&lt;P&gt;  Group 1       State:          Active&lt;/P&gt;&lt;P&gt;                Active time:    414641 (sec)&lt;/P&gt;&lt;P&gt;  Group 2       State:          Active&lt;/P&gt;&lt;P&gt;                Active time:    70040 (sec)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                slot 0: ASA5510 hw/sw rev (1.1/7.2(2)) status (Up Sys)&lt;/P&gt;&lt;P&gt;                  admin Interface outside (12.109.107.5): Normal&lt;/P&gt;&lt;P&gt;                  admin Interface inside (172.16.0.5): Normal&lt;/P&gt;&lt;P&gt;                  admin Interface DMZ (10.0.0.1): Normal&lt;/P&gt;&lt;P&gt;                  admin Interface management (172.16.255.51): Normal (Not-Monito&lt;/P&gt;&lt;P&gt;red)&lt;/P&gt;&lt;P&gt;                slot 1: ASA-SSM-10 hw/sw rev (1.0/5.0(2)S152.0) status&lt;/P&gt;&lt;P&gt;(Up/Up)&lt;/P&gt;&lt;P&gt;                  IPS, 5.0(2)S152.0, Up&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Other host:   Primary&lt;/P&gt;&lt;P&gt;  Group 1       State:          Standby Ready&lt;/P&gt;&lt;P&gt;                Active time:    0 (sec)&lt;/P&gt;&lt;P&gt;  Group 2       State:          Standby Ready&lt;/P&gt;&lt;P&gt;                Active time:    0 (sec)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                slot 0: ASA5510 hw/sw rev (1.1/7.2(2)) status (Up Sys)&lt;/P&gt;&lt;P&gt;                  admin Interface outside (12.109.107.24): Normal&lt;/P&gt;&lt;P&gt;                  admin Interface inside (172.16.0.24): Normal&lt;/P&gt;&lt;P&gt;                  admin Interface DMZ (10.0.0.2): Normal&lt;/P&gt;&lt;P&gt;                  admin Interface management (0.0.0.0): Normal&lt;/P&gt;&lt;P&gt;(Not-Monitored)&lt;/P&gt;&lt;P&gt;                slot 1: ASA-SSM-10 hw/sw rev (1.0/5.1(1)S205.0) status&lt;/P&gt;&lt;P&gt;(Up/Up)&lt;/P&gt;&lt;P&gt;                  IPS, 5.1(1)S205.0, Up&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stateful Failover Logical Update Statistics&lt;/P&gt;&lt;P&gt;        Link : FAILOVER Management0/0 (up)&lt;/P&gt;&lt;P&gt;        Stateful Obj    xmit       xerr       rcv        rerr&lt;/P&gt;&lt;P&gt;        General         105117     0          62565      0&lt;/P&gt;&lt;P&gt;        sys cmd         55988      0          55988      0&lt;/P&gt;&lt;P&gt;        up time         0          0          0          0&lt;/P&gt;&lt;P&gt;        RPC services    0          0          0          0&lt;/P&gt;&lt;P&gt;        TCP conn        2725       0          6299       0&lt;/P&gt;&lt;P&gt;        UDP conn        32         0          0          0&lt;/P&gt;&lt;P&gt;        ARP tbl         46372      0          278        0&lt;/P&gt;&lt;P&gt;        Xlate_Timeout   0          0          0          0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        Logical Update Queue Information&lt;/P&gt;&lt;P&gt;                        Cur     Max     Total&lt;/P&gt;&lt;P&gt;        Recv Q:         0       1       62565&lt;/P&gt;&lt;P&gt;        Xmit Q:         0       1       105117 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Jan 2007 14:23:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/active-active-failover-in-fwsm-silly-question/m-p/698021#M1029492</guid>
      <dc:creator>jim</dc:creator>
      <dc:date>2007-01-09T14:23:16Z</dc:date>
    </item>
    <item>
      <title>Re: Active/active failover in FWSM - silly question</title>
      <link>https://community.cisco.com/t5/network-security/active-active-failover-in-fwsm-silly-question/m-p/698022#M1029493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you, Jim&lt;/P&gt;&lt;P&gt;So, the active/active configuration means that each firewall can be primary for one context, and secondary for another context. It's just an active/standby config, but the primary and secondary roles can be allocated to firewalls per context. &lt;/P&gt;&lt;P&gt;I expected a different behavior, the active/active designation seemed to indicate that both firewalls can process traffic for the same context at the same time. &lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Cristian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jan 2007 13:22:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/active-active-failover-in-fwsm-silly-question/m-p/698022#M1029493</guid>
      <dc:creator>CRISTIAN LACATUS</dc:creator>
      <dc:date>2007-01-10T13:22:42Z</dc:date>
    </item>
  </channel>
</rss>

