<?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: esxi update and load balancing settings in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/esxi-update-and-load-balancing-settings/m-p/2966700#M287943</link>
    <description>&lt;P&gt;This issue is fixed in ESXi 7.0 Update 3m build-21686933 released TODAY 2023-05-03&lt;BR /&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3m-release-notes.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3m-release-notes.html&lt;/A&gt;&lt;BR /&gt;PR 3164897: After an upgrade to ESXi 7.0 Update 3l, some ESXi hosts and virtual machines connected to virtual switches might lose network&lt;BR /&gt;After an upgrade to ESXi 7.0 Update 3l, some ESXi hosts, their VMs, and other VMkernel ports, such as ports used by vSAN and vSphere Replication, which are connected to virtual switches, might lose connectivity due to an unexpected change in the NIC teaming policy. For example, the teaming policy on a portgroup might change to Route Based on Originating Virtual Port from Route Based on IP Hash. As a result, such a portgroup might lose network connectivity and some ESXi hosts and their VMs become inaccessible.&lt;/P&gt;&lt;P&gt;If you are already experiencing this problem, I do not believe that applying new release 7.0 U3m will revert any now-incorrect teaming policy back to what it was prior to your application of 7.0 U3l - you will likely need to do that manually. But honestly I have not yet applied U3m so I cannot say for sure.&lt;/P&gt;</description>
    <pubDate>Wed, 03 May 2023 20:25:55 GMT</pubDate>
    <dc:creator>PatrickDLong</dc:creator>
    <dc:date>2023-05-03T20:25:55Z</dc:date>
    <item>
      <title>esxi update and load balancing settings</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/esxi-update-and-load-balancing-settings/m-p/2966453#M287914</link>
      <description>&lt;P&gt;hello.&lt;/P&gt;&lt;P&gt;i have a strange problem&lt;/P&gt;&lt;P&gt;install update to my&amp;nbsp;&lt;SPAN&gt;VMware ESXi, 7.0.3, 18644231 hosts, after update&amp;nbsp;VMware ESXi, 7.0.3, 21424296&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;i have configured load balancing settings for vSwitch as Mac Hash, and doesn't have settings for port group.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;but after update, load balancing change for every port group to originating virtual port.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 May 2023 14:11:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/esxi-update-and-load-balancing-settings/m-p/2966453#M287914</guid>
      <dc:creator>Hanson2020</dc:creator>
      <dc:date>2023-05-02T14:11:24Z</dc:date>
    </item>
    <item>
      <title>Re: esxi update and load balancing settings</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/esxi-update-and-load-balancing-settings/m-p/2966700#M287943</link>
      <description>&lt;P&gt;This issue is fixed in ESXi 7.0 Update 3m build-21686933 released TODAY 2023-05-03&lt;BR /&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3m-release-notes.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3m-release-notes.html&lt;/A&gt;&lt;BR /&gt;PR 3164897: After an upgrade to ESXi 7.0 Update 3l, some ESXi hosts and virtual machines connected to virtual switches might lose network&lt;BR /&gt;After an upgrade to ESXi 7.0 Update 3l, some ESXi hosts, their VMs, and other VMkernel ports, such as ports used by vSAN and vSphere Replication, which are connected to virtual switches, might lose connectivity due to an unexpected change in the NIC teaming policy. For example, the teaming policy on a portgroup might change to Route Based on Originating Virtual Port from Route Based on IP Hash. As a result, such a portgroup might lose network connectivity and some ESXi hosts and their VMs become inaccessible.&lt;/P&gt;&lt;P&gt;If you are already experiencing this problem, I do not believe that applying new release 7.0 U3m will revert any now-incorrect teaming policy back to what it was prior to your application of 7.0 U3l - you will likely need to do that manually. But honestly I have not yet applied U3m so I cannot say for sure.&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2023 20:25:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/esxi-update-and-load-balancing-settings/m-p/2966700#M287943</guid>
      <dc:creator>PatrickDLong</dc:creator>
      <dc:date>2023-05-03T20:25:55Z</dc:date>
    </item>
  </channel>
</rss>

