<?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: Best option to configure FTD active/passive MAC in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/best-option-to-configure-ftd-active-passive-mac/m-p/4141653#M1073359</link>
    <description>The first commands one will change the mac address of the interface to the&lt;BR /&gt;one which you configure while the second command will use virtual mac&lt;BR /&gt;instead of changing the physical mac.&lt;BR /&gt;&lt;BR /&gt;Both of them are used for HA however, here is a scenario where the first&lt;BR /&gt;method will cause interruption while the second method won't.&lt;BR /&gt;&lt;BR /&gt;"if both units are not brought online at the same time and the secondary&lt;BR /&gt;unit boots first and becomes active, it uses the burned-in MAC addresses&lt;BR /&gt;for its own interfaces. When the primary unit comes online, the secondary&lt;BR /&gt;unit will obtain the MAC addresses from the primary unit. This change can&lt;BR /&gt;disrupt network traffic. Configuring virtual MAC addresses for the&lt;BR /&gt;interfaces ensures that the secondary unit uses the correct MAC address&lt;BR /&gt;when it is the active unit, even if it comes online before the primary unit.&lt;BR /&gt;"&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/A-H/cmdref1/f1.html#pgfId-2014020" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/A-H/cmdref1/f1.html#pgfId-2014020&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;*** please remember to rate useful posts&lt;BR /&gt;</description>
    <pubDate>Wed, 26 Aug 2020 13:00:01 GMT</pubDate>
    <dc:creator>Mohammed al Baqari</dc:creator>
    <dc:date>2020-08-26T13:00:01Z</dc:date>
    <item>
      <title>Best option to configure FTD active/passive MAC</title>
      <link>https://community.cisco.com/t5/network-security/best-option-to-configure-ftd-active-passive-mac/m-p/4141578#M1073348</link>
      <description>&lt;P&gt;What's the best way to configure static active/passive MAC address for a failover pair?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Asking, because there are basically two ways:&lt;/P&gt;&lt;P&gt;1) Under FTD interface configuration -&amp;gt; Advanced -. Active/Standby Mac address.&lt;/P&gt;&lt;P&gt;It is then being applied like this during deploy:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;FMC &amp;gt;&amp;gt; interface&amp;nbsp; XYZ&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;FMC &amp;gt;&amp;gt; no mac-address&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;FMC &amp;gt;&amp;gt; mac-address xxxx.xxxx.xxxx standby yyyy.yyyy.yyyy&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;... which does not look too reliable, as negating and then re-applying it on EACH deployment and, given one case I'm researching, not sure if that is not even leading to some interruptions, but I won't jump to any conclusions yet.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2) Configuration under High&amp;nbsp;&lt;/SPAN&gt;Availability -&amp;gt; Interface MAC Address table.&lt;/P&gt;&lt;P&gt;It is then being applied like this during deploy:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;FMC &amp;gt;&amp;gt; failover mac address XYZ xxxx.xxxx.xxxx yyyy.yyyy.yyyy&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;... again - on each deploy, but looks slightly cleaner as it is not negating and if the MAC hasn't changed, I'd say that re-applying this will not cause any issue. Haven't tried this out in a production.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If setting up both configuration options 1) comes first within the deploy and then when 2) follows, so the following Warning is shown:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ftd1 &amp;gt;&amp;gt; [info] : WARNING: MAC address already configured, single_vf interface IFNAME&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;...clearly using both of them does not look clean as well and is not even required as far as I see.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What's the best option here from reliability and stability perspective?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 10:11:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/best-option-to-configure-ftd-active-passive-mac/m-p/4141578#M1073348</guid>
      <dc:creator>niko</dc:creator>
      <dc:date>2020-08-26T10:11:13Z</dc:date>
    </item>
    <item>
      <title>Re: Best option to configure FTD active/passive MAC</title>
      <link>https://community.cisco.com/t5/network-security/best-option-to-configure-ftd-active-passive-mac/m-p/4141589#M1073351</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Option two is the best practice for HA because it eliminates the service&lt;BR /&gt;interruption due to mac change in case of failover.&lt;BR /&gt;&lt;BR /&gt;**** please remember to rate useful posts&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Aug 2020 10:39:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/best-option-to-configure-ftd-active-passive-mac/m-p/4141589#M1073351</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2020-08-26T10:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: Best option to configure FTD active/passive MAC</title>
      <link>https://community.cisco.com/t5/network-security/best-option-to-configure-ftd-active-passive-mac/m-p/4141592#M1073353</link>
      <description>&lt;P&gt;Thank you for input, but aren't both options eliminating service interruptions in case of failover? As per my understanding both options are used to configure active/standby MAC address and in case of failover they will behave the same way, but is there any behavioral difference then I'm not aware of?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 10:48:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/best-option-to-configure-ftd-active-passive-mac/m-p/4141592#M1073353</guid>
      <dc:creator>niko</dc:creator>
      <dc:date>2020-08-26T10:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: Best option to configure FTD active/passive MAC</title>
      <link>https://community.cisco.com/t5/network-security/best-option-to-configure-ftd-active-passive-mac/m-p/4141653#M1073359</link>
      <description>The first commands one will change the mac address of the interface to the&lt;BR /&gt;one which you configure while the second command will use virtual mac&lt;BR /&gt;instead of changing the physical mac.&lt;BR /&gt;&lt;BR /&gt;Both of them are used for HA however, here is a scenario where the first&lt;BR /&gt;method will cause interruption while the second method won't.&lt;BR /&gt;&lt;BR /&gt;"if both units are not brought online at the same time and the secondary&lt;BR /&gt;unit boots first and becomes active, it uses the burned-in MAC addresses&lt;BR /&gt;for its own interfaces. When the primary unit comes online, the secondary&lt;BR /&gt;unit will obtain the MAC addresses from the primary unit. This change can&lt;BR /&gt;disrupt network traffic. Configuring virtual MAC addresses for the&lt;BR /&gt;interfaces ensures that the secondary unit uses the correct MAC address&lt;BR /&gt;when it is the active unit, even if it comes online before the primary unit.&lt;BR /&gt;"&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/A-H/cmdref1/f1.html#pgfId-2014020" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/A-H/cmdref1/f1.html#pgfId-2014020&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;*** please remember to rate useful posts&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Aug 2020 13:00:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/best-option-to-configure-ftd-active-passive-mac/m-p/4141653#M1073359</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2020-08-26T13:00:01Z</dc:date>
    </item>
  </channel>
</rss>

