<?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: Lost Communication post vMotion in Networking Members</title>
    <link>https://communities.vmware.com/t5/Networking-Members/Lost-Communication-post-vMotion/m-p/2957715#M268</link>
    <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5179747"&gt;@santunezlenovo&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;This is mostly sure because of the port-security settings, as the MAC Address are advertised and allowed on a single port, when the vMotion happens the traffic is blocked. The good thing is that there is a KB from VMware explaining this:&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/1002811" target="_blank"&gt;https://kb.vmware.com/s/article/1002811&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Take a look with your network team to achieve the changes.&lt;/P&gt;</description>
    <pubDate>Fri, 03 Mar 2023 18:00:03 GMT</pubDate>
    <dc:creator>Lalegre</dc:creator>
    <dc:date>2023-03-03T18:00:03Z</dc:date>
    <item>
      <title>Lost Communication post vMotion</title>
      <link>https://communities.vmware.com/t5/Networking-Members/Lost-Communication-post-vMotion/m-p/2957441#M267</link>
      <description>&lt;P&gt;Hello Guys&lt;/P&gt;&lt;P&gt;I have an issue with some vsan nodes.&lt;/P&gt;&lt;P&gt;When vmotion is done from Node1 to Node3 the VMs keep responding and vice versa, but when I Vmotion to node 2 from node3 or node1 the VMs lose all communication. This only happens with node 2.&lt;/P&gt;&lt;P&gt;The 3 nodes are connected to a Cisco 9300L Switch.&lt;/P&gt;&lt;P&gt;I requested the switch configurations and they are not identical with node 2&lt;/P&gt;&lt;P&gt;Node 1 and Node 3 have these configuration on the switches&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;vMNIC1&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;interface GigabitEthernet2/0/X&lt;/LI&gt;&lt;LI&gt;switchport trunk native vlan 40&lt;/LI&gt;&lt;LI&gt;switchport trunk allowed vlan 40-42&lt;/LI&gt;&lt;LI&gt;switchport mode trunk&lt;/LI&gt;&lt;LI&gt;spanning-tree portfast&lt;/LI&gt;&lt;LI&gt;spanning-tree bpduguard enable&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;vMNIC3&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Interface GigabitEthernet1/0/X&lt;/LI&gt;&lt;LI&gt;switchport trunk native vlan 40&lt;/LI&gt;&lt;LI&gt;switchport trunk allowed vlan 40-42&lt;/LI&gt;&lt;LI&gt;switchport mode trunk&lt;/LI&gt;&lt;LI&gt;switchport port-security maximum 5&lt;/LI&gt;&lt;LI&gt;switchport port-security violation restrict&lt;/LI&gt;&lt;LI&gt;switchport port-security&lt;/LI&gt;&lt;LI&gt;storm-control broadcast level bps 2m 1m&lt;/LI&gt;&lt;LI&gt;storm-control multicast level bps 2m 1m&lt;/LI&gt;&lt;LI&gt;spanning-tree portfast&lt;/LI&gt;&lt;LI&gt;spanning-tree bpduguard enable&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;However, node 2 has these settings on the switch ports&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;vMNIC1 and vMNIC3 (Is the same configuration on the ports)&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;interface GigabitEthernet2/0/X&lt;/LI&gt;&lt;LI&gt;switchport trunk native vlan 40&lt;/LI&gt;&lt;LI&gt;switchport trunk allowed vlan 40-42&lt;/LI&gt;&lt;LI&gt;switchport mode trunk&lt;/LI&gt;&lt;LI&gt;spanning-tree portfast&lt;/LI&gt;&lt;LI&gt;spanning-tree bpduguard enable&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I have not been able to solve the problem, I can only think that it is a matter of configuration of the ports that must be configured identically, remove spanning-tree portfast.&lt;/P&gt;&lt;P&gt;The version of ESXi is 7.0.3 U3f and the vCenter 7.0.3&lt;/P&gt;&lt;P&gt;Thanks for your comments&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 13:07:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Networking-Members/Lost-Communication-post-vMotion/m-p/2957441#M267</guid>
      <dc:creator>santunezlenovo</dc:creator>
      <dc:date>2023-03-02T13:07:15Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Communication post vMotion</title>
      <link>https://communities.vmware.com/t5/Networking-Members/Lost-Communication-post-vMotion/m-p/2957715#M268</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5179747"&gt;@santunezlenovo&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;This is mostly sure because of the port-security settings, as the MAC Address are advertised and allowed on a single port, when the vMotion happens the traffic is blocked. The good thing is that there is a KB from VMware explaining this:&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/1002811" target="_blank"&gt;https://kb.vmware.com/s/article/1002811&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Take a look with your network team to achieve the changes.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 18:00:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Networking-Members/Lost-Communication-post-vMotion/m-p/2957715#M268</guid>
      <dc:creator>Lalegre</dc:creator>
      <dc:date>2023-03-03T18:00:03Z</dc:date>
    </item>
  </channel>
</rss>

