<?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: VM300 Live Migration - MS HyperV S2D - MAC Address/ MAC Spoofing in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/vm300-live-migration-ms-hyperv-s2d-mac-address-mac-spoofing/m-p/401854#M91748</link>
    <description>&lt;P&gt;Have you checked ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/set-up-the-vm-series-firewall-on-hyper-v.html" target="_blank"&gt;https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/set-up-the-vm-series-firewall-on-hyper-v.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also have you anabled promiscuous mode or copied the mac address that the Hyper-V gave to the VM?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/about-the-vm-series-firewall/hypervisor-assigned-mac-addresses.html" target="_blank"&gt;https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/about-the-vm-series-firewall/hypervisor-assigned-mac-addresses.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also have you tested with traditional NIC teaming and not SET as if the issue is with the SET teaming raise a case to Palo Alto TAC?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 26 Apr 2021 08:27:21 GMT</pubDate>
    <dc:creator>nikoolayy1</dc:creator>
    <dc:date>2021-04-26T08:27:21Z</dc:date>
    <item>
      <title>VM300 Live Migration - MS HyperV S2D - MAC Address/ MAC Spoofing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vm300-live-migration-ms-hyperv-s2d-mac-address-mac-spoofing/m-p/382622#M89869</link>
      <description>&lt;P&gt;We have a 4 node Hyper V S2D cluster with a single VM300 appliance.&amp;nbsp; We have been able to successfully live migrate the VM from node to node without any issues.&lt;/P&gt;&lt;P&gt;We are in the process of modifying the North / South network fabric.&amp;nbsp; I have successfully update the network on 3 of the 4 nodes.&amp;nbsp; When I went to do the final node (the node that the VM300 resides on), I live migrated the VM to one of the other nodes.&amp;nbsp; When I did the migration all network connectivity in and out of the PAN VM300 stopped.&lt;/P&gt;&lt;P&gt;Through troubleshooting it looked as though there was a possible issue with the way the MAC addresses of the appliance were setup.&lt;/P&gt;&lt;P&gt;Has anyone successfully setup a single VM300 in a HyperV cluster and was able to migrate from node to node?&amp;nbsp; What are the suggested MAC address settings in the appliance as well as the S2D cluster vNIC settings for the VM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Old Fabric:&lt;/P&gt;&lt;P&gt;-onboard intel nic (physical) connected to a single Cisco Nexus 9000 switch.&amp;nbsp; Using HyperV switch for VM traffic managment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;New Fabric&lt;/P&gt;&lt;P&gt;-Mellanox ConnectX 4LX NICs, connected to new Cisco Nexus 9000 switches.&amp;nbsp; Using a HyperV switch configured as a SET (Switch embedded teaming).&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2021 16:53:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vm300-live-migration-ms-hyperv-s2d-mac-address-mac-spoofing/m-p/382622#M89869</guid>
      <dc:creator>Dale.Johnson</dc:creator>
      <dc:date>2021-01-28T16:53:44Z</dc:date>
    </item>
    <item>
      <title>Re: VM300 Live Migration - MS HyperV S2D - MAC Address/ MAC Spoofing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vm300-live-migration-ms-hyperv-s2d-mac-address-mac-spoofing/m-p/401854#M91748</link>
      <description>&lt;P&gt;Have you checked ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/set-up-the-vm-series-firewall-on-hyper-v.html" target="_blank"&gt;https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/set-up-the-vm-series-firewall-on-hyper-v.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also have you anabled promiscuous mode or copied the mac address that the Hyper-V gave to the VM?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/about-the-vm-series-firewall/hypervisor-assigned-mac-addresses.html" target="_blank"&gt;https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/about-the-vm-series-firewall/hypervisor-assigned-mac-addresses.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also have you tested with traditional NIC teaming and not SET as if the issue is with the SET teaming raise a case to Palo Alto TAC?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Apr 2021 08:27:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vm300-live-migration-ms-hyperv-s2d-mac-address-mac-spoofing/m-p/401854#M91748</guid>
      <dc:creator>nikoolayy1</dc:creator>
      <dc:date>2021-04-26T08:27:21Z</dc:date>
    </item>
  </channel>
</rss>

