Assign L3 VN to Fabric Site - INFRA_VN

[initd-01]

Hello,

What's the best practice to assign the L3 VN "INFRA_VN" to a new fabric site?

When using the data source - like in the documentation - it's refered by the name as id hence the response is the name.

`data "catalystcenter_fabric_virtual_network" "example" {
  id = "SDA_VN1"
}

However using the resource to assign a vn to a fabric site, the id is required. Which is then still unknown.

resource "catalystcenter_virtual_network_to_fabric_site" "example" {
  virtual_network_name = "SDA_VN1"
  virtual_network_id   = "c782eff3-b743-4da2-a6ea-a27582a71287"
  fabric_site_id       = "5e6f7b3a-2b0b-4a7d-8b1c-0d4b1cd5e1b1"
}

Thanks for your help and sorry for the basic question.

[initd-01]

The output for the INFRA_VN looks like this:

data "catalystcenter_fabric_virtual_network" "infra_vn" {
  id = "INFRA_VN"
}
output "infra_vn" {
  value = data.catalystcenter_fabric_virtual_network.infra_vn
}

  - infra_vn         = {
      - id                   = "INFRA_VN"
      - is_guest             = false
      - sg_names             = null
      - virtual_network_name = "INFRA_VN"
      - vmanage_vpn_id       = ""
    } -> null

[kuba-mazurkiewicz]

@initd-01 , use this resource:

resource "catalystcenter_fabric_l3_virtual_network" "example" {
virtual_network_name = "INFRA_VN"
fabric_ids = ["5e6f7b3a-2b0b-4a7d-8b1c-0d4b1cd5e1b1"]
}

This resource is using new API endpoint for creating and assiging L3_VN to fabric_site in one call.

API endpoint:

/dna/intent/api/v1/sda/layer3VirtualNetworks

[initd-01]

Thanks for your response. I've tried this resource and got the following issue:

│ Error: Client Error
│ 
│   with catalystcenter_fabric_l3_virtual_network.vn["INFRA_VN"],
│   on main.tf line 162, in resource "catalystcenter_fabric_l3_virtual_network" "vn":
│  162: resource "catalystcenter_fabric_l3_virtual_network" "vn" {
│ 
│ Failed to configure object (PUT), got error: task '0198f554-f211-7888-b6c5-2c510f4aae47' failed: TASK_MODIFY_PUT, Provisioning failed due to an invalid parameter.
│ Cannot delete the Virtual Network that is used for L3 handoff.,
│ {"response":{"version":1756462645101,"startTime":1756462641681,"endTime":1756462645101,"progress":"TASK_MODIFY_PUT","data":"workflow_id=75dbfb1a-6fc8-4601-b72d-2ff46b3454e9;cfs_id=0;rollback_status=not_supported;rollback_taskid=0;failure_task=Validation
│ of business
│ intent:35d9f98b-0e42-4143-81f7-35811fbd33a0;processcfs_complete=false","errorCode":"NCSO20401","lastUpdate":1756462645084,"serviceType":"NCSP","failureReason":"Provisioning
│ failed due to an invalid parameter. Cannot delete the Virtual Network that is used for L3
│ handoff.","isError":true,"instanceTenantId":"64959bab8b4d6344be1c1c73","id":"0198f554-f211-7888-b6c5-2c510f4aae47"},"version":"1.0"}

I have other fabrics sites already on my cc which use the INFRA_VN. Any idea on how to handle this case?

[kuba-mazurkiewicz]

you need to add all fabric_ids which has this L3VN:

resource "catalystcenter_fabric_l3_virtual_network" "example" {
virtual_network_name = "INFRA_VN"
fabric_ids = ["5e6f7b3a-2b0b-4a7d-8b1c-0d4b1cd5e1b1", "XXXXX", "XXXXX"]
}