<?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: Updating VSAN stretched cluster vCenter Foundation in VMware vSAN Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2980748#M15438</link>
    <description>&lt;P&gt;a vSAN witness appliance still runs ESXi at it's core. I suspect that this is why you're getting the license breach. I'm not entirely sure if this will ever work properly.&lt;/P&gt;&lt;P&gt;Your best bet here would be to contact support.&lt;/P&gt;</description>
    <pubDate>Fri, 04 Aug 2023 07:53:37 GMT</pubDate>
    <dc:creator>Brisk</dc:creator>
    <dc:date>2023-08-04T07:53:37Z</dc:date>
    <item>
      <title>Updating VSAN stretched cluster vCenter Foundation</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2979689#M15410</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;we have a customer that uses two 2-node VSAN clusters in one vCenter.&lt;/P&gt;&lt;P&gt;vCenter Foundation&lt;BR /&gt;Cluster 1: 2 Servers with VSAN Witness Appliance on datacenter level&lt;BR /&gt;Cluster 2: 2 Servers with VSAN Witness Appliance on datacenter level&lt;/P&gt;&lt;P&gt;When they updated their environment, updating the ESX-Servers went smooth.&lt;/P&gt;&lt;P&gt;However, after they patched one of their Witness Appliances, vCenter regognized the rebooting Witness as full ESX-Host, and since vCenter Foundation can only manage 4 ESX Hosts, the Witness Appliance got disconnected which left VSAN in Error state.&lt;/P&gt;&lt;P&gt;The only way to solve this was to temporarily change the vCenter license to Standard and add the virtual Witness. After adding, changing back to Foundation worked without issues.&lt;/P&gt;&lt;P&gt;Was this a stupid coincidence or did anybody have similar issues?&lt;/P&gt;&lt;P&gt;I found similar things when building 2+2+1 Stretched Clusters from scratch, and the workaround was to add the Witness Appliance to vCenter before the physical hosts. However this one doesn't work in production environment.&lt;/P&gt;&lt;P&gt;Thanks everybody&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2023 13:03:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2979689#M15410</guid>
      <dc:creator>badkapp</dc:creator>
      <dc:date>2023-07-28T13:03:42Z</dc:date>
    </item>
    <item>
      <title>Re: Updating VSAN stretched cluster vCenter Foundation</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2980748#M15438</link>
      <description>&lt;P&gt;a vSAN witness appliance still runs ESXi at it's core. I suspect that this is why you're getting the license breach. I'm not entirely sure if this will ever work properly.&lt;/P&gt;&lt;P&gt;Your best bet here would be to contact support.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Aug 2023 07:53:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2980748#M15438</guid>
      <dc:creator>Brisk</dc:creator>
      <dc:date>2023-08-04T07:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: Updating vSAN stretched cluster vCenter Foundation</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2985600#M15562</link>
      <description>&lt;P&gt;I recall when I worked at VMware that this came up, and there was fix for it accomplished with a vCenter Server update.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;What version of vSphere/vSAN?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 19:49:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2985600#M15562</guid>
      <dc:creator>Jasemccarty</dc:creator>
      <dc:date>2023-09-06T19:49:37Z</dc:date>
    </item>
    <item>
      <title>Re: Updating vSAN stretched cluster vCenter Foundation</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2985610#M15563</link>
      <description>&lt;P&gt;&lt;SPAN&gt;This was indeed an issue that has been fixed in vSphere 6.5 U2, and 6.7 U1 (see &lt;/SPAN&gt;&lt;A title="https://docs.vmware.com/en/VMware-vSphere/6.7/rn/vsphere-vcenter-server-671-release-notes.html" href="https://docs.vmware.com/en/VMware-vSphere/6.7/rn/vsphere-vcenter-server-671-release-notes.html" rel="nofollow noopener noreferrer" target="_blank"&gt;VMware vCenter Server 6.7 Update 1 Release Notes&lt;/A&gt;&lt;SPAN&gt; )&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 21:01:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2985610#M15563</guid>
      <dc:creator>MJMSRI</dc:creator>
      <dc:date>2023-09-06T21:01:47Z</dc:date>
    </item>
    <item>
      <title>Re: Updating VSAN stretched cluster vCenter Foundation</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2985692#M15570</link>
      <description>&lt;P&gt;Just an FYI, while I am aware this documentation refers to vCenter Essentials (limited to managing 3 physical hosts), it is likely this would also apply to vCenter Foundation (but with 4 physical hosts):&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsan/vmware-vsan-licensing-guide.pdf" target="_blank" rel="noopener"&gt;https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsan/vmware-vsan-licensing-guide.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;"• The vSAN witness appliance must be added to vCenter prior&lt;BR /&gt;to the third physical host being added to vCenter.&lt;BR /&gt;• A warning message will be generated when attempting to add&lt;BR /&gt;the vSAN witness appliance as a vSAN witness host after the three&lt;BR /&gt;physical hosts have been added.&lt;BR /&gt;Note: The order of operation is important; vCenter does not recognize the&lt;BR /&gt;vSAN witness appliance as a virtual host until after it is added to vCenter"&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 10:59:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Updating-VSAN-stretched-cluster-vCenter-Foundation/m-p/2985692#M15570</guid>
      <dc:creator>TheBobkin</dc:creator>
      <dc:date>2023-09-07T10:59:18Z</dc:date>
    </item>
  </channel>
</rss>

