NSX-T Automation with Terraform

Here are some of the Terraform script used to automate NSX-T.

Creation of multiple static routes using .csv file
Creation of multiple logical segments using .csv file

1) Creation of Multiple Static Routes

This Terraform file required the following,

Terraform version 0.13 and above
Terraform NSX-T Provider

It make use the csvdecode Terraform function.

Files

Put the following files in the working directory

main.tf
variable.tf
version.tf
terraform.tfvars
static_route.tf
static_route.csv

main.tf

The main.tf file is use to define connection to NSX-T Manager.

/* 
  Main file connecting to NSX Manager
*/

# Define Provider 
provider "nsxt" {
  host                  = var.nsx_manager
  username              = var.nsx_username
  password              = var.nsx_password
  allow_unverified_ssl  = true
  max_retries           = 10
  retry_min_delay       = 500
  retry_max_delay       = 5000
  retry_on_status_codes = [429]
}

version.tf

The version.tf file defined the minimum version of Terraform and provider to use.

terraform {
  required_providers {
    nsxt = {
      source = "terraform-providers/nsxt"
    }
  }
  required_version = ">= 0.13"
}

variable.tf

The variable.tf file defined the variable used.

/*
   Variable definition.
   Can be define in single or separate file(s)
   Input Variable will obtain from, 
   1) .tfvars file 
   2) if variable in not found in .tfvars
   3) it will look for local machine environment variable TF_VAR_<variable>="<value>"
   4) lastly it will prompt for value of the variable
*/

variable "nsx_manager" {
  description = "IP or FQDN of NSX Manager"
  type        = string
}

variable "nsx_username" {
  description = "The admin username of NSX Manager"
  type        = string
}

variable "nsx_password" {
  description = "The admin password of NSX Manager"
  type        = string
}

terraform.tfvars

The terraform.tfvars file defined the input variable.

# Insert the IP address or hostname of the NSX-T Manager
nsx_manager = "172.16.1.31"

# Insert the usreanme of the NSX-T Manager
nsx_username = "admin"

# Password recommended to use encrypted secret or input prompt
nsx_password = "VMware1!VMware1!"

static_route.tf

The static_route.tf file defined the code to automate the creation of static routes.

/* 
  Configure multiple static routes using CSV file 
*/

# Define Tier0 Gateway Data Source
data "nsxt_policy_tier0_gateway" "provider-t0-gateway" {
  display_name = "provider-t0-gateway"
}

# Import CSV file "static_route.csv" in local directory
# Using csvdecode function
locals {
csv_data = file("static_route.csv")
instances = csvdecode(local.csv_data)
}


# Define Resource
resource "nsxt_policy_static_route" "staticRoute" {
  for_each = { for inst in local.instances : inst.id => inst }
  display_name = each.value.display_name
  gateway_path = data.nsxt_policy_tier0_gateway.provider-t0-gateway.path
  network      = each.value.network

  next_hop {
    admin_distance = "1"
    ip_address     = each.value.next_hop_ip
  }
}

static_route.csv

The static_route.csv file defined the static routes in Comma-separated format.

id,display_name,network,next_hop_ip
1,T1_web_segment,10.150.2.0/24,10.10.10.1
2,T1_app_segment,10.160.0.0/16,10.10.10.1
3,T1_db_segment,10.170.0.0/16,10.10.20.1
4,T2_web_segment,10.180.100.0/24,10.10.50.254
5,T3_app_segement,10.202.20.0/24,10.10.50.254

Terraform Command

Before run the Terraform command, below are the screen capture of the NSX-T Screen.

terraform init

Use the terraform init command to initialize a working directory containing Terraform configuration files.

./terraform init                                                            ✔ 

Initializing the backend...

Initializing provider plugins...
- Using previously-installed terraform-providers/nsxt v2.1.1

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, we recommend adding version constraints in a required_providers block
in your configuration, with the constraint strings suggested below.

* terraform-providers/nsxt: version = "~> 2.1.1"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

terraform plan

Use the terraform plan command to create an execution plan and to check if the changes matches your expectations without making any actual changes.

./terraform plan  

Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

data.nsxt_policy_tier0_gateway.provider-t0-gateway: Refreshing state...

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # nsxt_policy_static_route.staticRoute["1"] will be created
  + resource "nsxt_policy_static_route" "staticRoute" {
      + display_name = "T1_web_segment"
      + gateway_path = "/infra/tier-0s/provider-t0-gateway"
      + id           = (known after apply)
      + network      = "10.150.2.0/24"
      + nsx_id       = (known after apply)
      + path         = (known after apply)
      + revision     = (known after apply)

      + next_hop {
          + admin_distance = 1
          + ip_address     = "10.10.10.1"
        }
    }

  # nsxt_policy_static_route.staticRoute["2"] will be created
  + resource "nsxt_policy_static_route" "staticRoute" {
      + display_name = "T1_app_segment"
      + gateway_path = "/infra/tier-0s/provider-t0-gateway"
      + id           = (known after apply)
      + network      = "10.160.0.0/16"
      + nsx_id       = (known after apply)
      + path         = (known after apply)
      + revision     = (known after apply)

      + next_hop {
          + admin_distance = 1
          + ip_address     = "10.10.10.1"
        }
    }

  # nsxt_policy_static_route.staticRoute["3"] will be created
  + resource "nsxt_policy_static_route" "staticRoute" {
      + display_name = "T1_db_segment"
      + gateway_path = "/infra/tier-0s/provider-t0-gateway"
      + id           = (known after apply)
      + network      = "10.170.0.0/16"
      + nsx_id       = (known after apply)
      + path         = (known after apply)
      + revision     = (known after apply)

      + next_hop {
          + admin_distance = 1
          + ip_address     = "10.10.20.1"
        }
    }

  # nsxt_policy_static_route.staticRoute["4"] will be created
  + resource "nsxt_policy_static_route" "staticRoute" {
      + display_name = "T2_web_segment"
      + gateway_path = "/infra/tier-0s/provider-t0-gateway"
      + id           = (known after apply)
      + network      = "10.180.100.0/24"
      + nsx_id       = (known after apply)
      + path         = (known after apply)
      + revision     = (known after apply)

      + next_hop {
          + admin_distance = 1
          + ip_address     = "10.10.50.254"
        }
    }

  # nsxt_policy_static_route.staticRoute["5"] will be created
  + resource "nsxt_policy_static_route" "staticRoute" {
      + display_name = "T3_app_segement"
      + gateway_path = "/infra/tier-0s/provider-t0-gateway"
      + id           = (known after apply)
      + network      = "10.202.20.0/24"
      + nsx_id       = (known after apply)
      + path         = (known after apply)
      + revision     = (known after apply)

      + next_hop {
          + admin_distance = 1
          + ip_address     = "10.10.50.254"
        }
    }

Plan: 5 to add, 0 to change, 0 to destroy.

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.

terraform apply

Use the terraform apply command to apply the changes.

./terraform apply  

data.nsxt_policy_tier0_gateway.provider-t0-gateway: Refreshing state...

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # nsxt_policy_static_route.staticRoute["1"] will be created
  + resource "nsxt_policy_static_route" "staticRoute" {
      + display_name = "T1_web_segment"
      + gateway_path = "/infra/tier-0s/provider-t0-gateway"
      + id           = (known after apply)
      + network      = "10.150.2.0/24"
      + nsx_id       = (known after apply)
      + path         = (known after apply)
      + revision     = (known after apply)

      + next_hop {
          + admin_distance = 1
          + ip_address     = "10.10.10.1"
        }
    }

  # nsxt_policy_static_route.staticRoute["2"] will be created
  + resource "nsxt_policy_static_route" "staticRoute" {
      + display_name = "T1_app_segment"
      + gateway_path = "/infra/tier-0s/provider-t0-gateway"
      + id           = (known after apply)
      + network      = "10.160.0.0/16"
      + nsx_id       = (known after apply)
      + path         = (known after apply)
      + revision     = (known after apply)

      + next_hop {
          + admin_distance = 1
          + ip_address     = "10.10.10.1"
        }
    }

  # nsxt_policy_static_route.staticRoute["3"] will be created
  + resource "nsxt_policy_static_route" "staticRoute" {
      + display_name = "T1_db_segment"
      + gateway_path = "/infra/tier-0s/provider-t0-gateway"
      + id           = (known after apply)
      + network      = "10.170.0.0/16"
      + nsx_id       = (known after apply)
      + path         = (known after apply)
      + revision     = (known after apply)

      + next_hop {
          + admin_distance = 1
          + ip_address     = "10.10.20.1"
        }
    }

  # nsxt_policy_static_route.staticRoute["4"] will be created
  + resource "nsxt_policy_static_route" "staticRoute" {
      + display_name = "T2_web_segment"
      + gateway_path = "/infra/tier-0s/provider-t0-gateway"
      + id           = (known after apply)
      + network      = "10.180.100.0/24"
      + nsx_id       = (known after apply)
      + path         = (known after apply)
      + revision     = (known after apply)

      + next_hop {
          + admin_distance = 1
          + ip_address     = "10.10.50.254"
        }
    }

  # nsxt_policy_static_route.staticRoute["5"] will be created
  + resource "nsxt_policy_static_route" "staticRoute" {
      + display_name = "T3_app_segement"
      + gateway_path = "/infra/tier-0s/provider-t0-gateway"
      + id           = (known after apply)
      + network      = "10.202.20.0/24"
      + nsx_id       = (known after apply)
      + path         = (known after apply)
      + revision     = (known after apply)

      + next_hop {
          + admin_distance = 1
          + ip_address     = "10.10.50.254"
        }
    }

Plan: 5 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

nsxt_policy_static_route.staticRoute["3"]: Creating...
nsxt_policy_static_route.staticRoute["4"]: Creating...
nsxt_policy_static_route.staticRoute["5"]: Creating...
nsxt_policy_static_route.staticRoute["2"]: Creating...
nsxt_policy_static_route.staticRoute["1"]: Creating...
nsxt_policy_static_route.staticRoute["3"]: Creation complete after 0s [id=27fba098-5db4-49a6-a794-0a74aa8ee441]
nsxt_policy_static_route.staticRoute["4"]: Creation complete after 0s [id=6bcb09ec-188b-4b19-8ac9-cc5352988bbf]
nsxt_policy_static_route.staticRoute["5"]: Creation complete after 1s [id=838536e3-f5ea-43a1-8597-f4fdba76db11]
nsxt_policy_static_route.staticRoute["2"]: Creation complete after 1s [id=0153db95-e555-471f-9e51-5b3d01b57b17]
nsxt_policy_static_route.staticRoute["1"]: Creation complete after 1s [id=75f5171f-7ee7-483e-a308-581413e034a7]

Apply complete! Resources: 5 added, 0 changed, 0 destroyed.

To Delete Multiple Static Routes

Use terraform show command to inspect the current state as Terraform sees it.

./terraform show

# data.nsxt_policy_tier0_gateway.provider-t0-gateway:
data "nsxt_policy_tier0_gateway" "provider-t0-gateway" {
    display_name = "provider-t0-gateway"
    id           = "provider-t0-gateway"
    path         = "/infra/tier-0s/provider-t0-gateway"
}

# nsxt_policy_static_route.staticRoute["1"]:
resource "nsxt_policy_static_route" "staticRoute" {
    display_name = "T1_web_segment"
    gateway_path = "/infra/tier-0s/provider-t0-gateway"
    id           = "75f5171f-7ee7-483e-a308-581413e034a7"
    network      = "10.150.2.0/24"
    nsx_id       = "75f5171f-7ee7-483e-a308-581413e034a7"
    path         = "/infra/tier-0s/provider-t0-gateway/static-routes/75f5171f-7ee7-483e-a308-581413e034a7"
    revision     = 0

    next_hop {
        admin_distance = 1
        ip_address     = "10.10.10.1"
    }
}

# nsxt_policy_static_route.staticRoute["2"]:
resource "nsxt_policy_static_route" "staticRoute" {
    display_name = "T1_app_segment"
    gateway_path = "/infra/tier-0s/provider-t0-gateway"
    id           = "0153db95-e555-471f-9e51-5b3d01b57b17"
    network      = "10.160.0.0/16"
    nsx_id       = "0153db95-e555-471f-9e51-5b3d01b57b17"
    path         = "/infra/tier-0s/provider-t0-gateway/static-routes/0153db95-e555-471f-9e51-5b3d01b57b17"
    revision     = 0

    next_hop {
        admin_distance = 1
        ip_address     = "10.10.10.1"
    }
}

# nsxt_policy_static_route.staticRoute["3"]:
resource "nsxt_policy_static_route" "staticRoute" {
    display_name = "T1_db_segment"
    gateway_path = "/infra/tier-0s/provider-t0-gateway"
    id           = "27fba098-5db4-49a6-a794-0a74aa8ee441"
    network      = "10.170.0.0/16"
    nsx_id       = "27fba098-5db4-49a6-a794-0a74aa8ee441"
    path         = "/infra/tier-0s/provider-t0-gateway/static-routes/27fba098-5db4-49a6-a794-0a74aa8ee441"
    revision     = 0

    next_hop {
        admin_distance = 1
        ip_address     = "10.10.20.1"
    }
}

# nsxt_policy_static_route.staticRoute["4"]:
resource "nsxt_policy_static_route" "staticRoute" {
    display_name = "T2_web_segment"
    gateway_path = "/infra/tier-0s/provider-t0-gateway"
    id           = "6bcb09ec-188b-4b19-8ac9-cc5352988bbf"
    network      = "10.180.100.0/24"
    nsx_id       = "6bcb09ec-188b-4b19-8ac9-cc5352988bbf"
    path         = "/infra/tier-0s/provider-t0-gateway/static-routes/6bcb09ec-188b-4b19-8ac9-cc5352988bbf"
    revision     = 0

    next_hop {
        admin_distance = 1
        ip_address     = "10.10.50.254"
    }
}

# nsxt_policy_static_route.staticRoute["5"]:
resource "nsxt_policy_static_route" "staticRoute" {
    display_name = "T3_app_segement"
    gateway_path = "/infra/tier-0s/provider-t0-gateway"
    id           = "838536e3-f5ea-43a1-8597-f4fdba76db11"
    network      = "10.202.20.0/24"
    nsx_id       = "838536e3-f5ea-43a1-8597-f4fdba76db11"
    path         = "/infra/tier-0s/provider-t0-gateway/static-routes/838536e3-f5ea-43a1-8597-f4fdba76db11"
    revision     = 0

    next_hop {
        admin_distance = 1
        ip_address     = "10.10.50.254"
    }
}

terraform plan -destroy

Use terraform plan -destroy command to check if the destroy changes matches your expectations without making any actual changes.

./terraform plan -destroy                                                       

Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

data.nsxt_policy_tier0_gateway.provider-t0-gateway: Refreshing state... [id=provider-t0-gateway]
nsxt_policy_static_route.staticRoute["3"]: Refreshing state... [id=27fba098-5db4-49a6-a794-0a74aa8ee441]
nsxt_policy_static_route.staticRoute["4"]: Refreshing state... [id=6bcb09ec-188b-4b19-8ac9-cc5352988bbf]
nsxt_policy_static_route.staticRoute["5"]: Refreshing state... [id=838536e3-f5ea-43a1-8597-f4fdba76db11]
nsxt_policy_static_route.staticRoute["2"]: Refreshing state... [id=0153db95-e555-471f-9e51-5b3d01b57b17]
nsxt_policy_static_route.staticRoute["1"]: Refreshing state... [id=75f5171f-7ee7-483e-a308-581413e034a7]

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # nsxt_policy_static_route.staticRoute["1"] will be destroyed
  - resource "nsxt_policy_static_route" "staticRoute" {
      - display_name = "T1_web_segment" -> null
      - gateway_path = "/infra/tier-0s/provider-t0-gateway" -> null
      - id           = "75f5171f-7ee7-483e-a308-581413e034a7" -> null
      - network      = "10.150.2.0/24" -> null
      - nsx_id       = "75f5171f-7ee7-483e-a308-581413e034a7" -> null
      - path         = "/infra/tier-0s/provider-t0-gateway/static-routes/75f5171f-7ee7-483e-a308-581413e034a7" -> null
      - revision     = 0 -> null

      - next_hop {
          - admin_distance = 1 -> null
          - ip_address     = "10.10.10.1" -> null
        }
    }

 [ ----- output omitted --------] 

Plan: 0 to add, 0 to change, 5 to destroy.

terraform destroy

Use terraform destroy command to destroy the Terraform-managed infrastructure.

./terraform destroy                                                             
data.nsxt_policy_tier0_gateway.provider-t0-gateway: Refreshing state... [id=provider-t0-gateway]
nsxt_policy_static_route.staticRoute["1"]: Refreshing state... [id=75f5171f-7ee7-483e-a308-581413e034a7]
nsxt_policy_static_route.staticRoute["2"]: Refreshing state... [id=0153db95-e555-471f-9e51-5b3d01b57b17]
nsxt_policy_static_route.staticRoute["3"]: Refreshing state... [id=27fba098-5db4-49a6-a794-0a74aa8ee441]
nsxt_policy_static_route.staticRoute["5"]: Refreshing state... [id=838536e3-f5ea-43a1-8597-f4fdba76db11]
nsxt_policy_static_route.staticRoute["4"]: Refreshing state... [id=6bcb09ec-188b-4b19-8ac9-cc5352988bbf]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # nsxt_policy_static_route.staticRoute["1"] will be destroyed
  - resource "nsxt_policy_static_route" "staticRoute" {
      - display_name = "T1_web_segment" -> null
      - gateway_path = "/infra/tier-0s/provider-t0-gateway" -> null
      - id           = "75f5171f-7ee7-483e-a308-581413e034a7" -> null
      - network      = "10.150.2.0/24" -> null
      - nsx_id       = "75f5171f-7ee7-483e-a308-581413e034a7" -> null
      - path         = "/infra/tier-0s/provider-t0-gateway/static-routes/75f5171f-7ee7-483e-a308-581413e034a7" -> null
      - revision     = 0 -> null

      - next_hop {
          - admin_distance = 1 -> null
          - ip_address     = "10.10.10.1" -> null
        }
    }

 [ ----- output omitted ------- ]

Plan: 0 to add, 0 to change, 5 to destroy.

Do you really want to destroy all resources?
  Terraform will destroy all your managed infrastructure, as shown above.
  There is no undo. Only 'yes' will be accepted to confirm.

  Enter a value: yes

nsxt_policy_static_route.staticRoute["3"]: Destroying... [id=27fba098-5db4-49a6-a794-0a74aa8ee441]
nsxt_policy_static_route.staticRoute["4"]: Destroying... [id=6bcb09ec-188b-4b19-8ac9-cc5352988bbf]
nsxt_policy_static_route.staticRoute["2"]: Destroying... [id=0153db95-e555-471f-9e51-5b3d01b57b17]
nsxt_policy_static_route.staticRoute["5"]: Destroying... [id=838536e3-f5ea-43a1-8597-f4fdba76db11]
nsxt_policy_static_route.staticRoute["1"]: Destroying... [id=75f5171f-7ee7-483e-a308-581413e034a7]
nsxt_policy_static_route.staticRoute["3"]: Destruction complete after 1s
nsxt_policy_static_route.staticRoute["4"]: Destruction complete after 1s
nsxt_policy_static_route.staticRoute["2"]: Destruction complete after 1s
nsxt_policy_static_route.staticRoute["5"]: Destruction complete after 1s
nsxt_policy_static_route.staticRoute["1"]: Destruction complete after 1s

Destroy complete! Resources: 5 destroyed.

2) Creation of Multiple Logical Segments

This Terraform file required the following,

Terraform version 0.13 and above
Terraform NSX-T Provider

It make use the csvdecode Terraform function.

Files

Put the following files in the working directory

main.tf
variable.tf
version.tf
terraform.tfvars
logical_segment.tf
logical_segment.csv

The main.tf, variable.tf, version.tf and terraform.tfvars file remain the same.

logical_segment.tf

The logical_segment.tf file defined the code to automate the creation of logical segment.

/*
  Configure multiple NSX-T Segment using CSV file
*/

# Define Data Source for Tier1 Gateway
data "nsxt_policy_tier1_gateway" "tenant1-t1-gw" {
  display_name = "tenant1-t1-gw"
}

# Define Data Source for Transport Zone
data "nsxt_policy_transport_zone" "tz-overlay" {
  display_name = "tz-overlay"
}

# Import CSV file "segment.csv" in local directory
# Using csvdecode function
locals {
csv_data = file("logical_segment.csv")
instances = csvdecode(local.csv_data)
}


# Define Resource
resource "nsxt_policy_segment" "segment" {
  for_each = { for inst in local.instances : inst.id => inst }
  display_name = each.value.display_name
  connectivity_path   = data.nsxt_policy_tier1_gateway.tenant1-t1-gw.path
  transport_zone_path = data.nsxt_policy_transport_zone.tz-overlay.path

  subnet {
     # Define Gatewy IP in cidr format
     cidr =  each.value.cidr
  }

}

Terraform Command

Use the terraform init command to initialize a working directory containing Terraform configuration files. Use the terraform plan command to create an execution plan and to check if the changes matches your expectations without making any actual changes.

./terraform plan                                                                              
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

data.nsxt_policy_transport_zone.tz-overlay: Refreshing state...
data.nsxt_policy_tier1_gateway.tenant1-t1-gw: Refreshing state...

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # nsxt_policy_segment.segment["1"] will be created
  + resource "nsxt_policy_segment" "segment" {
      + connectivity_path   = "/infra/tier-1s/tenant1-t1-gw"
      + display_name        = "web_segment"
      + id                  = (known after apply)
      + nsx_id              = (known after apply)
      + overlay_id          = (known after apply)
      + path                = (known after apply)
      + revision            = (known after apply)
      + transport_zone_path = "/infra/sites/default/enforcement-points/default/transport-zones/7b4a0333-a217-40f8-8e3c-d848d8ff4fdf"

      + subnet {
          + cidr    = "10.156.1.1/24"
          + network = (known after apply)
        }
    }

  # nsxt_policy_segment.segment["2"] will be created
  + resource "nsxt_policy_segment" "segment" {
      + connectivity_path   = "/infra/tier-1s/tenant1-t1-gw"
      + display_name        = "app_sgement"
      + id                  = (known after apply)
      + nsx_id              = (known after apply)
      + overlay_id          = (known after apply)
      + path                = (known after apply)
      + revision            = (known after apply)
      + transport_zone_path = "/infra/sites/default/enforcement-points/default/transport-zones/7b4a0333-a217-40f8-8e3c-d848d8ff4fdf"

      + subnet {
          + cidr    = "10.156.2.1/24"
          + network = (known after apply)
        }
    }

  # nsxt_policy_segment.segment["3"] will be created
  + resource "nsxt_policy_segment" "segment" {
      + connectivity_path   = "/infra/tier-1s/tenant1-t1-gw"
      + display_name        = "db_segment"
      + id                  = (known after apply)
      + nsx_id              = (known after apply)
      + overlay_id          = (known after apply)
      + path                = (known after apply)
      + revision            = (known after apply)
      + transport_zone_path = "/infra/sites/default/enforcement-points/default/transport-zones/7b4a0333-a217-40f8-8e3c-d848d8ff4fdf"

      + subnet {
          + cidr    = "10.156.3.1/24"
          + network = (known after apply)
        }
    }

Plan: 3 to add, 0 to change, 0 to destroy.

Use the terraform apply command to apply the changes.

/terraform apply                                                                              ✔  3662  17:12:20
data.nsxt_policy_tier1_gateway.tenant1-t1-gw: Refreshing state...
data.nsxt_policy_transport_zone.tz-overlay: Refreshing state...

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # nsxt_policy_segment.segment["1"] will be created
  + resource "nsxt_policy_segment" "segment" {
      + connectivity_path   = "/infra/tier-1s/tenant1-t1-gw"
      + display_name        = "web_segment"
      + id                  = (known after apply)
      + nsx_id              = (known after apply)
      + overlay_id          = (known after apply)
      + path                = (known after apply)
      + revision            = (known after apply)
      + transport_zone_path = "/infra/sites/default/enforcement-points/default/transport-zones/7b4a0333-a217-40f8-8e3c-d848d8ff4fdf"

      + subnet {
          + cidr    = "10.156.1.1/24"
          + network = (known after apply)
        }
    }

[ ----- output omitted ----- ] 

nsxt_policy_segment.segment["3"]: Creating...
nsxt_policy_segment.segment["2"]: Creating...
nsxt_policy_segment.segment["1"]: Creating...
nsxt_policy_segment.segment["2"]: Creation complete after 1s [id=738942e2-ef94-4430-aafe-42088fbb8f55]
nsxt_policy_segment.segment["1"]: Creation complete after 1s [id=58695444-e9ee-43f5-af58-a03671fe5af5]
nsxt_policy_segment.segment["3"]: Creation complete after 1s [id=fbfbfbac-43e7-4cff-b6c8-603e577fab12]

Apply complete! Resources: 3 added, 0 changed, 0 destroyed.

Use terraform destroy command to destroy the Terraform-managed infrastructure.

./terraform destroy                                                                         
data.nsxt_policy_tier1_gateway.tenant1-t1-gw: Refreshing state... [id=tenant1-t1-gw]
data.nsxt_policy_transport_zone.tz-overlay: Refreshing state... [id=7b4a0333-a217-40f8-8e3c-d848d8ff4fdf]
nsxt_policy_segment.segment["3"]: Refreshing state... [id=fbfbfbac-43e7-4cff-b6c8-603e577fab12]
nsxt_policy_segment.segment["2"]: Refreshing state... [id=738942e2-ef94-4430-aafe-42088fbb8f55]
nsxt_policy_segment.segment["1"]: Refreshing state... [id=58695444-e9ee-43f5-af58-a03671fe5af5]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # nsxt_policy_segment.segment["1"] will be destroyed
  - resource "nsxt_policy_segment" "segment" {
      - connectivity_path   = "/infra/tier-1s/tenant1-t1-gw" -> null
      - display_name        = "web_segment" -> null
      - id                  = "58695444-e9ee-43f5-af58-a03671fe5af5" -> null
      - nsx_id              = "58695444-e9ee-43f5-af58-a03671fe5af5" -> null
      - path                = "/infra/segments/58695444-e9ee-43f5-af58-a03671fe5af5" -> null
      - revision            = 0 -> null
      - transport_zone_path = "/infra/sites/default/enforcement-points/default/transport-zones/7b4a0333-a217-40f8-8e3c-d848d8ff4fdf" -> null

      - subnet {
          - cidr        = "10.156.1.1/24" -> null
          - dhcp_ranges = [] -> null
          - network     = "10.156.1.0/24" -> null
        }
    }


[ ----- output omitted ----- ]

nsxt_policy_segment.segment["2"]: Destroying... [id=738942e2-ef94-4430-aafe-42088fbb8f55]
nsxt_policy_segment.segment["1"]: Destroying... [id=58695444-e9ee-43f5-af58-a03671fe5af5]
nsxt_policy_segment.segment["3"]: Destroying... [id=fbfbfbac-43e7-4cff-b6c8-603e577fab12]
nsxt_policy_segment.segment["1"]: Destruction complete after 2s
nsxt_policy_segment.segment["3"]: Destruction complete after 2s
nsxt_policy_segment.segment["2"]: Destruction complete after 2s

Destroy complete! Resources: 3 destroyed.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Repository files navigation

NSX-T Automation with Terraform

1) Creation of Multiple Static Routes

Files

main.tf

version.tf

variable.tf

terraform.tfvars

static_route.tf

static_route.csv

Terraform Command

terraform init

terraform plan

terraform apply

To Delete Multiple Static Routes

terraform plan -destroy

terraform destroy

2) Creation of Multiple Logical Segments

Files

logical_segment.tf

Terraform Command

About

Uh oh!

Releases

Packages

Languages

Name		Name	Last commit message	Last commit date
Latest commit History 21 Commits
images		images
README.md		README.md
logical_segment.csv		logical_segment.csv
logical_segment.tf		logical_segment.tf
main.tf		main.tf
static_route.csv		static_route.csv
static_route.tf		static_route.tf
terraform.tfvars		terraform.tfvars
variable.tf		variable.tf
versions.tf		versions.tf

thesplithorizon/Terraform-NSX-T

Folders and files

Latest commit

History

Repository files navigation

NSX-T Automation with Terraform

1) Creation of Multiple Static Routes

Files

main.tf

version.tf

variable.tf

terraform.tfvars

static_route.tf

static_route.csv

Terraform Command

terraform init

terraform plan

terraform apply

To Delete Multiple Static Routes

terraform plan -destroy

terraform destroy

2) Creation of Multiple Logical Segments

Files

logical_segment.tf

Terraform Command

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages