<?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 Hi Again :)  Lets say that in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732212#M192621</link>
    <description>&lt;P&gt;Hi Again &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Lets say that the primary IP is 1.1.1.x (ASA1)&amp;nbsp;and the secondary IP is 1.1.1.y(ASA2)&amp;nbsp;You connect to 1.1.1.y which is in standby mode, you issue the command "failover active" and it will disconnect your session.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now, to verify that it actually worked, you need to connect to 1.1.1.x and you should see that it says&amp;nbsp;&lt;/P&gt;&lt;P&gt;ASA/sec/act and if you connect to 1.1.1.y (previously ASA2) it should say ASA/pri/sta.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This behavior is the correct one. If you are seeing something different, let me know.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 19 Aug 2015 16:26:39 GMT</pubDate>
    <dc:creator>Maykol Rojas</dc:creator>
    <dc:date>2015-08-19T16:26:39Z</dc:date>
    <item>
      <title>Why command "failover active" cannot change active/standby ?</title>
      <link>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732211#M192620</link>
      <description>&lt;P&gt;Hi We have failover pair ASA 5555(ASA1 and ASA2). After we configured failover, we cannot switch active/standby by command &lt;STRONG&gt;failover active&lt;/STRONG&gt;. When I use the command in ASA2(in standby status), it can only change Secondary status into Primary status. When I re-used the command, the Primary change back into Secondary, the standby status in ASA2 remain unchanged. Anyone can explain it ? Thank you&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:27:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732211#M192620</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2019-03-12T06:27:33Z</dc:date>
    </item>
    <item>
      <title>Hi Again :)  Lets say that</title>
      <link>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732212#M192621</link>
      <description>&lt;P&gt;Hi Again &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Lets say that the primary IP is 1.1.1.x (ASA1)&amp;nbsp;and the secondary IP is 1.1.1.y(ASA2)&amp;nbsp;You connect to 1.1.1.y which is in standby mode, you issue the command "failover active" and it will disconnect your session.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now, to verify that it actually worked, you need to connect to 1.1.1.x and you should see that it says&amp;nbsp;&lt;/P&gt;&lt;P&gt;ASA/sec/act and if you connect to 1.1.1.y (previously ASA2) it should say ASA/pri/sta.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This behavior is the correct one. If you are seeing something different, let me know.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Aug 2015 16:26:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732212#M192621</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2015-08-19T16:26:39Z</dc:date>
    </item>
    <item>
      <title>Thank you so much for your</title>
      <link>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732213#M192622</link>
      <description>&lt;P&gt;Thank you so much for your reply. Yes, I got exact same result as you said. In other word, after I used command failover active in ASA2(in standby status), two ASA's pri/sec changed, instead of act/sta.&amp;nbsp;but I remember(not sure)in long time ago,&amp;nbsp;after&amp;nbsp;I&amp;nbsp;used&amp;nbsp;the command "failover active" in ASA2(when it is in standby), the ASA2 show "ASA/sec/act", instead of "ASA/pri/sta".&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Aug 2015 16:53:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732213#M192622</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2015-08-19T16:53:19Z</dc:date>
    </item>
    <item>
      <title>That can be the confusing</title>
      <link>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732214#M192623</link>
      <description>&lt;P&gt;That can be the confusing part. I see what you are saying,however, whenever you connect to 1.1.1.x should always take you to the unit that is active, no matter if it is the primary unit or the secondary unit.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Per your statement, it is working as expected.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mike.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Aug 2015 17:08:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732214#M192623</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2015-08-19T17:08:48Z</dc:date>
    </item>
    <item>
      <title>So that means the command</title>
      <link>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732215#M192624</link>
      <description>&lt;P&gt;Thank you so much. just understood&lt;/P&gt;</description>
      <pubDate>Thu, 20 Aug 2015 18:59:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-command-quot-failover-active-quot-cannot-change-active/m-p/2732215#M192624</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2015-08-20T18:59:59Z</dc:date>
    </item>
  </channel>
</rss>

