NSX-T T-0 External Segement

[DineshReddy1205]

Hi Team ,

I am not using any VLAN tagging in my env .Segments are configured using VYOS Router .

I am trying to configure t-0 interface Segment but it's failing with following error -

•  [error_code=10140, module_name=ROUTING, error_message='[Routing] Logical-Switch-vlan vlan-ids:[0] of LogicalSwitch/80a43589-c737-428b-8923-68e8c89a41cc conflicts with another VLAN sharing same underlying Edge host-switch is not allowed. Change vlan configuration.']
  • [Routing] Logical-Switch-vlan vlan-ids:[0] of LogicalSwitch/80a43589-c737-428b-8923-68e8c89a41cc conflicts with another VLAN sharing same underlying Edge host-switch is not allowed. Change vlan configuration.

Please let me know how to fix above error .

[dragance]

Hello, you have multiple options but I will share some of them:

I - connect edge node uplinks on TRUNK VLAN segments inside NSX / create additional VLAN Segments for external connectivity per Vlans that you're using / you can use same TEP pool for transport nodes and edges in this design - little bad decision is that Edges are "sitting" inside NSX actually;

II - create PG on vDS used by Edge nodes as Trunk / create uplink profile for Edges with Overlay VLAN in it and 1-2 named Vlans for external connectivity (like in picture), per your design / create segments for external connectivity - you will need to use different IP TEP pools for edges and transport nodes.

HTH,

Dragan

 

[engyak]

Is this with NSX-T 3.1 or greater? I recall being permitted to do this with 3.1 but it's not listed under the patch notes.

[dragance]

Yes, I didn't check but think it's been possible from even older version, as only regular option for edge N-S networking. Later MTEP, with single IP pool for transport and edge nodes is also possible, using only one VLAN.

BR,

Dragan