<?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: Failover replication of interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/failover-replication-of-interface/m-p/1509176#M616798</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As commands are entered in the active ASA, the commands should be replicated on the standby unit.&amp;nbsp; The following is mentioned in the configuration guide:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;Command replication always flows from the active&amp;nbsp; unit to the standby unit. As commands are entered on the active unit,&amp;nbsp; they are sent across the failover link to the standby unit. You do not&amp;nbsp; have to save the active configuration to Flash memory to replicate the&amp;nbsp; commands.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_active_standby.html#wp1079487"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_active_standby.html#wp1079487&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So changing the interface parameters on the active ASA should be replicated to the standby unit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;Changing the duplex or speed of the interface will not perform a shut/no shut on the interface, but it will interrupt traffic since the interface will try to detect the settings of the switchport it's connected to and renegotiate.&amp;nbsp; For example, if the switchport is configured for auto duplex, and on the ASA you switch the duplex setting from full duplex to half duplex, a little time is needed for the switchport interface to negotiate to half duplex in order to match the ASA.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Therefore, it's probably best to make these changes after hours or during a maintenance window.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 13 Nov 2010 19:25:24 GMT</pubDate>
    <dc:creator>Allen P Chen</dc:creator>
    <dc:date>2010-11-13T19:25:24Z</dc:date>
    <item>
      <title>Failover replication of interface</title>
      <link>https://community.cisco.com/t5/network-security/failover-replication-of-interface/m-p/1509175#M616749</link>
      <description>&lt;P&gt;i would like to know if the firewall is configured in failover and if i am changing the speed or duplex of any data interface (eg:gig0/1) of the unit acting as Active , will it get replicated to standby unit ? Also , if it doesnot gets replicated , will any of the units will give a warning stating that "interface is not in sync with each other ".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also if i am changing the speed / duplex of a particular interface in the active unit , will the connections continue to traverse across or is it like that they would come to halt or teardown due to interface parameters&amp;nbsp; being changed . what i mean over here is will changing the parameters will do a kind of shut and unshut the interface for that moment ?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:09:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-replication-of-interface/m-p/1509175#M616749</guid>
      <dc:creator>jvardhan29</dc:creator>
      <dc:date>2019-03-11T19:09:06Z</dc:date>
    </item>
    <item>
      <title>Re: Failover replication of interface</title>
      <link>https://community.cisco.com/t5/network-security/failover-replication-of-interface/m-p/1509176#M616798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As commands are entered in the active ASA, the commands should be replicated on the standby unit.&amp;nbsp; The following is mentioned in the configuration guide:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;Command replication always flows from the active&amp;nbsp; unit to the standby unit. As commands are entered on the active unit,&amp;nbsp; they are sent across the failover link to the standby unit. You do not&amp;nbsp; have to save the active configuration to Flash memory to replicate the&amp;nbsp; commands.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_active_standby.html#wp1079487"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ha_active_standby.html#wp1079487&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So changing the interface parameters on the active ASA should be replicated to the standby unit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;Changing the duplex or speed of the interface will not perform a shut/no shut on the interface, but it will interrupt traffic since the interface will try to detect the settings of the switchport it's connected to and renegotiate.&amp;nbsp; For example, if the switchport is configured for auto duplex, and on the ASA you switch the duplex setting from full duplex to half duplex, a little time is needed for the switchport interface to negotiate to half duplex in order to match the ASA.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Therefore, it's probably best to make these changes after hours or during a maintenance window.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 13 Nov 2010 19:25:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/failover-replication-of-interface/m-p/1509176#M616798</guid>
      <dc:creator>Allen P Chen</dc:creator>
      <dc:date>2010-11-13T19:25:24Z</dc:date>
    </item>
  </channel>
</rss>

