<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>EVC on Brisk-IT</title>
    <link>https://brisk-it.net/tags/evc/</link>
    <description>Recent content in EVC on Brisk-IT</description>
    <generator>Hugo -- 0.149.0</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 28 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://brisk-it.net/tags/evc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VCF 9.x - Enable EVC after deploy</title>
      <link>https://brisk-it.net/vcf9x-enable-evc-after-deploy/</link>
      <pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://brisk-it.net/vcf9x-enable-evc-after-deploy/</guid>
      <description>&lt;p&gt;One thing I like to do whenever I bring up a new cluster, is to enable EVC on it. The past years I&amp;rsquo;ve seen mixed generation clusters a lot and there&amp;rsquo;s no reason to leave it disabled on new clusters. Doing it at deploy will save you &lt;em&gt;A LOT&lt;/em&gt; of headaches down the line, having to power off an entire cluster is no fun.&lt;/p&gt;
&lt;p&gt;Something I found out recently is that the VCF Installer does not enable EVC during the deployment of a new VCF environment, you also can&amp;rsquo;t make the installer do it through the API. This is outlined in this &lt;a href=&#34;https://knowledge.broadcom.com/external/article/447772/how-to-enable-evc-during-vmware-cloud-fo.html&#34;&gt;Broadcom KB&lt;/a&gt;. The KB tells us how we can enable EVC during the deployment phase, but what if, like me, you only find out after deployment? And what if this happens on your management cluster, and vCenter also doesn&amp;rsquo;t have EVC enabled? Well, we can use per-vm EVC for that!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
