<?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 Thanks thiland...Once I in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636696#M200810</link>
    <description>&lt;P&gt;Thanks thiland...&lt;/P&gt;&lt;P&gt;Once I create and join Blue to group-2, where do I trigger the failover for group-2 from?&lt;/P&gt;&lt;P&gt;Do I trigger the failover from the Security context, or from the Blue context? {suspect it is from the Security context?!!}&lt;/P&gt;&lt;P&gt;My window is at 2AM!&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Apr 2015 18:15:09 GMT</pubDate>
    <dc:creator>highmiles2</dc:creator>
    <dc:date>2015-04-22T18:15:09Z</dc:date>
    <item>
      <title>Firewall Security Context Failover</title>
      <link>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636694#M200749</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have a Cisco 5585 running in multi context mode with 4 contexts enabled: Admin, Red, Blue, White&lt;/P&gt;&lt;P&gt;All contexts are assigned to join-failover-group 1&lt;/P&gt;&lt;P&gt;All contexts are currently Active in Primary firewall&lt;/P&gt;&lt;P&gt;Would I be able to failover &lt;U&gt;just&lt;/U&gt; the Blue context and make it Active in Secondary FW?&lt;/P&gt;&lt;P&gt;And how?&lt;/P&gt;&lt;P&gt;If I log in to the Active Blue context and issue "failover exec standby failover active", would this cause all group 1 members to failover to Secondary or just the Blue context?&lt;/P&gt;&lt;P&gt;I am reluctant to try this in an production environment and find out that I have to failover the entire group-1.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:49:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636694#M200749</guid>
      <dc:creator>highmiles2</dc:creator>
      <dc:date>2019-03-12T05:49:16Z</dc:date>
    </item>
    <item>
      <title>You would need to setup your</title>
      <link>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636695#M200769</link>
      <description>&lt;P&gt;You would need to setup your second failover group and assign 'Blue' to it in the system context:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family:courier new,courier,monospace;"&gt;failover group 2&lt;BR /&gt;&amp;nbsp; replication http&lt;BR /&gt;&amp;nbsp; polltime interface msec 500 holdtime 5&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family:courier new,courier,monospace;"&gt;context BLUE&lt;BR /&gt;&amp;nbsp; join-failover-group 2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Context failovers are based on failover-group membership, so all of them would failover.&lt;BR /&gt;Also I would wait until a change window to do any failover reconfiguration or testing.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Apr 2015 18:08:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636695#M200769</guid>
      <dc:creator>thiland</dc:creator>
      <dc:date>2015-04-22T18:08:23Z</dc:date>
    </item>
    <item>
      <title>Thanks thiland...Once I</title>
      <link>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636696#M200810</link>
      <description>&lt;P&gt;Thanks thiland...&lt;/P&gt;&lt;P&gt;Once I create and join Blue to group-2, where do I trigger the failover for group-2 from?&lt;/P&gt;&lt;P&gt;Do I trigger the failover from the Security context, or from the Blue context? {suspect it is from the Security context?!!}&lt;/P&gt;&lt;P&gt;My window is at 2AM!&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Apr 2015 18:15:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636696#M200810</guid>
      <dc:creator>highmiles2</dc:creator>
      <dc:date>2015-04-22T18:15:09Z</dc:date>
    </item>
    <item>
      <title>You'd do it from the system</title>
      <link>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636697#M200828</link>
      <description>&lt;P&gt;You'd do it from the system context and specify the group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So if you were on the 02 ASA:&lt;/P&gt;&lt;P&gt;changeto system&lt;/P&gt;&lt;P&gt;failover active group 2&lt;/P&gt;</description>
      <pubDate>Wed, 22 Apr 2015 18:30:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636697#M200828</guid>
      <dc:creator>thiland</dc:creator>
      <dc:date>2015-04-22T18:30:50Z</dc:date>
    </item>
    <item>
      <title>Yep...that worked.Thanks</title>
      <link>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636698#M200839</link>
      <description>&lt;P&gt;Yep...that worked.&lt;/P&gt;&lt;P&gt;Thanks thiland for your quick and prompt reply.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2015 18:05:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-security-context-failover/m-p/2636698#M200839</guid>
      <dc:creator>highmiles2</dc:creator>
      <dc:date>2015-04-24T18:05:29Z</dc:date>
    </item>
  </channel>
</rss>

