<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vcf9.1 on SDN-Warrior | Daniel Krieger</title>
    <link>https://sdn-warrior.org/tags/vcf9.1/</link>
    <description>Recent content in Vcf9.1 on SDN-Warrior | Daniel Krieger</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <copyright>Daniel Krieger</copyright>
    <lastBuildDate>Tue, 05 May 2026 16:00:00 +0200</lastBuildDate>
    <atom:link href="https://sdn-warrior.org/tags/vcf9.1/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VCF 9.1 - VPCs Connectivity Policies</title>
      <link>https://sdn-warrior.org/posts/vcf9.1-vpcs-connectivity-policy/</link>
      <pubDate>Tue, 05 May 2026 16:00:00 +0200</pubDate>
      <guid>https://sdn-warrior.org/posts/vcf9.1-vpcs-connectivity-policy/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;A new VCF release is just around the corner, and just like the transition from VCF 5.X to 9.0, this one brings massive changes as well. Not only is the entire fleet being turned upside down, but there have also been a ton of changes to my favorite topic: VPCs in NSX. One of the many new features is VPC Connectivity Policies. Today, in this blog post, I’ll explain what you can do with them and how they work. So let&amp;rsquo;s dive into VPC&amp;rsquo;s rabbit hole.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
