NSX-T on MichelleWayZ | Michelle Goossens | Blog

Unable to connect vSphereVM to NSX-T Segment in Terraform

Thu, 17 Apr 2025 08:30:00 +0000

Hi,

Recently while rebuilding the lab, I came across what seems to be a bug between the hashicorp/vsphere and the vmware/nsxt terraform providers.

For example, here's a snippet from code that should work, but doesn't:

 1resource "nsxt_policy_segment" "testinglinuxlab1" {
 2 display_name = "testinglinuxlab1"
 3 transport_zone_path = data.nsxt_policy_transport_zone.overlay_tz.path
 4 connectivity_path = data.nsxt_policy_tier1_gateway.T1Main.path
 5
 6 subnet {
 7 cidr = "10.183.94.1/24"
 8 }
 9}
10
11resource "vsphere_virtual_machine" "testinglinuxlab101" {
12 name = "testing-linuxlab1-01"
13 resource_pool_id = data.vsphere_compute_cluster.AVA.resource_pool_id
14 datastore_id = data.vsphere_datastore.ssd.id
15
16 num_cpus = 2
17 memory = 2048 # in MB
18 guest_id = data.vsphere_virtual_machine.debian12-template.guest_id
19
20 network_interface {
21 network_id = resource.nsxt_policy_segment.testinglinuxlab1.id
22 adapter_type = data.vsphere_virtual_machine.debian12-template.network_interface_types[0]
23 }
24
25 disk {
26 label = "disk0"
27 size = "50" # In GB
28 eagerly_scrub = false
29 thin_provisioned = true
30 }
31
32 clone {
33 template_uuid = data.vsphere_virtual_machine.debian12-template.id
34
35 customize {
36 linux_options {
37 host_name = "testing-test01"
38 domain = "ava.michellegoossens.com"
39 }
40
41 network_interface {
42 ipv4_address = "10.183.94.10"
43 ipv4_netmask = 24
44 dns_server_list = [ "192.168.74.112" ]
45 }
46
47 ipv4_gateway = "10.183.94.1"
48 }
49 }
50 lifecycle {
51 ignore_changes = [
52 clone[0].template_uuid
53 ]
54 }
55}

This is because the vSphere provider wants a dvPortgroup ID, but the NSX-T provider doesn't give that nor has an option (from what I could find) to give this.

NSX-T Data Center: Tier 0 Router not showing up in VPN Service dropdown

Sat, 30 Jan 2021 23:46:37 +0000

Hi everyone,

In this post, I want to highlight an issue I had.

I wanted to create a VPN Service, connected to a Tier 0 gateway. But none of my tier 0 gateways would show up. I couldn’t find any information on this, not even in the documentation (it’s well hidden and unless you know what to look for, it’s not easily found).

I attempted to make an API call, and this is when I found the solution to my issue. I made a PUT request to:

In-place upgrading a NSX-T ESXi Host with multiple host switches.

Wed, 08 Jul 2020 23:53:19 +0000

Hi everyone,

Here is how I upgraded my NSX-T deployment from 3.0.0 to 3.0.1.

If you tried to in-place update a NSX-T Host that has multiple host switches, you will get an error. You can use this trick to get around this limitation.

First, we log into the NSX-T Manager, and go to the Upgrade tab under system. Here, we upload the file and continues with the upgrade.
We upgrade like normal until we get on the hosts tab. We SSH into the host and we first visit this URL: http://:8080/repository/metadata/manifest
This file contains the link to the zip file that we need to wget in /tmp on the ESXi host. Then we run:

Moved from NSX-T back to NSX-V

Wed, 04 Dec 2019 00:27:00 +0000

Hi everyone,

This post will be out about me moving back from NSX-T to NSX-V due to weird deploying issues.

NSX-V is no longer being developed, so this has caused me to try to migrate to the new NSX-T, however I moved back to NSX-V when my NSX-T Edge nodes started to fail. The Geneve tunnels to the ESXi host randomly started to stop working and asking on the VMTN NSX forums did not work either as I got no response after four days and I needed my virtual networking to work again, so I figured that it would be easier to migrate back to NSX-V until I reinstall ESXi on the host.