Same here:
Mar 27, 2025, 2:50:00 PM : [error_code=10140, module_name=ROUTING, error_message='[Routing] [Logical-Switch-trunk-vlan ([[2310, 2310], [2320, 2320]]) of LogicalSwitch/92d389dd-4e20-4b74-9950-dd3c1caf4d9d] overlapping with [Logical-Switch-trunk-vlan of LogicalSwitch/1ff17184-40b2-42a0-83d1-0e592b38c300] in same underlying Edge host-switch is not allowed. Change vlan configuration.', error_code=10140, module_name=ROUTING, error_message='[Routing] [Logical-Switch-trunk-vlan ([[2310, 2310], [2320, 2320]]) of LogicalSwitch/92d389dd-4e20-4b74-9950-dd3c1caf4d9d] overlapping with [Logical-Switch-vlan of LogicalSwitch/1ff17184-40b2-42a0-83d1-0e592b38c300] in same underlying Edge host-switch is not allowed. Change vlan configuration.']
There is no LogicalSwitch or Ports with that VLANs inside interface of NSX. Is there anything that we can do to fix that issue?
Original Message:
Sent: Feb 18, 2025 08:55 AM
From: Christophe NIEL
Subject: possible stale realized config ?
Hello,
I have a T0 I created in a lab, which has seen upgrades from v2 to v4 as we are trying a few things
the T0 is in error with a message I found here a few times
[error_code=10140, module_name=ROUTING, error_message='[Routing] [Logical-Switch-trunk-vlan of LogicalSwitch/65efc389-5ca6-4219-9e81-b4f66dc1c32a] and [Logical-Switch-vlan of df8591e6-1082-4ff9-934d-b4c9e1918394] having same vlan-ids:[[1711, 1713]] in same underlying Edge host-switch is not allowed. Change vlan configuration.']
these vlan 1711 and 1713 were uplink vlan segment for T0-VRF I was trying to automate with terraform for nsx, deleting things and replaying the terraform project (trying to automate the T0-VRF, the T1, the vcloud tenant, attaching all that together)
I combed all the config, I even dumped all the corfu database and look in all the files extracted, nowhere are these ID present (vlan ID or logical switch ID)
I can rebuild the whole platform, it's only a small lab, but the problem is bothering me, how to find these "same vlan-ids" when they don't exists
is there a way to check if something is stale, or "force" the T0 to refresh its config between the realized state and the configuration?