<?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>NSX on Route179</title>
    <link>https://route179.dev/tags/nsx/</link>
    <description>Recent content in NSX on Route179</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>2026 Sheng Chen</copyright>
    <lastBuildDate>Mon, 02 May 2022 18:41:08 +0000</lastBuildDate>
    <atom:link href="https://route179.dev/tags/nsx/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Integrate F5 Load Balancers into VMware Cloud on AWS SDDC Environment</title>
      <link>https://route179.dev/2022/05/02/integrate-f5-load-balancers-into-vmware-cloud-on-aws-sddc-environment/</link>
      <pubDate>Mon, 02 May 2022 18:41:08 +0000</pubDate>
      <guid>https://route179.dev/2022/05/02/integrate-f5-load-balancers-into-vmware-cloud-on-aws-sddc-environment/</guid>
      <description>&lt;p&gt;With the recent release of &lt;a href=&#34;https://docs.vmware.com/en/VMware-Cloud-on-AWS/0/rn/vmc-on-aws-relnotes.html#wn04052022&#34;&gt;&lt;strong&gt;VMware Cloud on AWS SDDC version 1.18&lt;/strong&gt;&lt;/a&gt;, we have introduced a ton of advanced networking capabilities which opened up possibilities for many new interesting use cases. Customers can now utilise the NSX Manager UI (or VMC Policy API) to configure route aggregation at each SDDC level, and this provides an efficient way to solve the &lt;a href=&#34;https://kb.vmware.com/s/article/78931&#34;&gt;100 DX route limit&lt;/a&gt;. Customer can also create additional Tier-1 Compute Gateways (Multi-CGWs) with static route injection capabilities to address different requirements such as network multi-tenancy, overlapping IPv4 environments and integrating with 3rd-party network &amp;amp; security appliances etc. You can read more details about the new features &lt;a href=&#34;https://blogs.vmware.com/cloud/2022/04/06/vmware-cloud-on-aws-advanced-networking-and-routing-features/&#34;&gt;at here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>NSX-T Automation with Terraform</title>
      <link>https://route179.dev/2020/10/02/nsx-t-automation-with-terraform/</link>
      <pubDate>Fri, 02 Oct 2020 10:16:46 +0000</pubDate>
      <guid>https://route179.dev/2020/10/02/nsx-t-automation-with-terraform/</guid>
      <description>&lt;p&gt;Recently I have tried out the Terraform NSX-T Provider and it worked like a charm. In this post, I will demonstrate a simple example on how to leverage Terraform to provision a basic NSX tenant network environment, which includes the following:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;create a Tier-1 router&lt;/li&gt;
&lt;li&gt;create (linked) routed ports on the new T1 router and the existing upstream T0 router&lt;/li&gt;
&lt;li&gt;link the T1 router to the upstream T0 router&lt;/li&gt;
&lt;li&gt;create three logical switches with three logical ports&lt;/li&gt;
&lt;li&gt;create three downlink LIFs (with subnets/gateway defined) on the T1 router, and link each of them to the logical switch ports accordingly&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Once the tenant environment is provisioned by Terraform, the 3x tenant subnets will be automatically published to the T0 router and propagated to the rest of the network (if BGP is enabled), and we should be able to reach the individual LIF addresses. Below is a sample topology deployed in my lab — (here I’m using pre-provisioned static routes between the T0 and upstream network for simplicity reasons).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
