<?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: HA1 not UP when HA interfaces have same mac address in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ha1-not-up-when-ha-interfaces-have-same-mac-address/m-p/542651#M111139</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/72965"&gt;@Sam_Rosaldo&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Do you have promiscuous mode enabled? While I haven't worked with RHOSP it seems to me like you maybe don't have promiscuous mode enabled on the hypervisor or RHOSP is like AWS and Azure and simply can't function with interfaces sharing the same MAC address.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 18 May 2023 20:44:27 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2023-05-18T20:44:27Z</dc:date>
    <item>
      <title>HA1 not UP when HA interfaces have same mac address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ha1-not-up-when-ha-interfaces-have-same-mac-address/m-p/542599#M111133</link>
      <description>&lt;P&gt;Hello Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope you can help us, We're also already planning to create a TAC case for this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have provisioned 2 vFW on RHOSP.&lt;BR /&gt;We configured the 2 fw on HA Active-passive.&lt;BR /&gt;HA1 &amp;gt; e1/8&lt;BR /&gt;HA1 Back-up &amp;gt; e1/9&lt;/P&gt;
&lt;P&gt;Now the data interfaces e1/1 to 1/7 has to have same mac address right for HA failover to be seamless as per below link&lt;/P&gt;
&lt;P&gt;We have disable port security on RHOSP as this is an equivalent of promiscuous mode in VMWARE.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://sso.paloaltonetworks.com/app/panw-ciam_sfdcknowledgecommunity_1/exk3jjgpeeZioKZWj0j6/sso/saml?RelayState=https://knowledgebase.paloaltonetworks.com/kcSArticleDetail?id=kA10g000000PLZy" target="_blank" rel="nofollow noopener noreferrer"&gt;https://sso.paloaltonetworks.com/app/panw-ciam_sfdcknowledgecommunity_1/exk3jjgpeeZioKZWj0j6/sso/sam...&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;As per our observation, even after following the above, HA1 is still not UP.&lt;BR /&gt;And the MAC address of HA interfaces e1/8 and e1/9 are the same on FW1 and FW2. This is what we think is causing the HA interfaces to not go UP because as per checking on other HA FW, their HA interfaces on data interfaces dont have the same MAC Address.&lt;/P&gt;
&lt;P&gt;Troublshooting done:&lt;BR /&gt;Reboot both vFW&lt;BR /&gt;Reconfigure HA.&lt;/P&gt;
&lt;P&gt;Enable Use hypervisor assigne MAC Address.&lt;BR /&gt;&amp;gt;HA went UP and worked fine since e1/8 and e1/9 now have different MAC address.&lt;/P&gt;
&lt;P&gt;Disable Use hypervisor assigne MAC Address.&lt;BR /&gt;&amp;gt;HA went down since both FW now have same MAC address again.&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2023 11:43:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ha1-not-up-when-ha-interfaces-have-same-mac-address/m-p/542599#M111133</guid>
      <dc:creator>Sam_Rosaldo</dc:creator>
      <dc:date>2023-05-18T11:43:26Z</dc:date>
    </item>
    <item>
      <title>Re: HA1 not UP when HA interfaces have same mac address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ha1-not-up-when-ha-interfaces-have-same-mac-address/m-p/542651#M111139</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/72965"&gt;@Sam_Rosaldo&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Do you have promiscuous mode enabled? While I haven't worked with RHOSP it seems to me like you maybe don't have promiscuous mode enabled on the hypervisor or RHOSP is like AWS and Azure and simply can't function with interfaces sharing the same MAC address.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2023 20:44:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ha1-not-up-when-ha-interfaces-have-same-mac-address/m-p/542651#M111139</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2023-05-18T20:44:27Z</dc:date>
    </item>
    <item>
      <title>Re: HA1 not UP when HA interfaces have same mac address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ha1-not-up-when-ha-interfaces-have-same-mac-address/m-p/542681#M111148</link>
      <description>&lt;P&gt;As per rhosp team, they already disabled the port security which they said is equal to VMware promiscuous mode enabled.&lt;/P&gt;
&lt;P&gt;We already resolved the same MAC address, it seems the team hasnt uploaded the vmfw license. Ater the license is uploaded the MAC address change. Although HA1 -Backup (e1/8) and H2(e1/9) interface is still not UP.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 May 2023 05:04:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ha1-not-up-when-ha-interfaces-have-same-mac-address/m-p/542681#M111148</guid>
      <dc:creator>Sam_Rosaldo</dc:creator>
      <dc:date>2023-05-19T05:04:54Z</dc:date>
    </item>
  </channel>
</rss>

