I've noticed that I can create several Logical Switches using the same name.
¿Is this a correct behavior or is it a bug?
I'm testing it in NSX ver 6.2.4.4292526
Thanks,
D.
Since they are using same name, you would want to connect to the correct VNI (Segment ID).
Logical Switch with same name is technically possible but yes I agree with you that the platform should not allow for a same name just like the vDS dvPortGroup.
You could probably file a feature request to VMware: Making a VMware feature request (1002123) | VMware KB
I'm using different NSX version and confirm can create multiple logical switches with same name
The logical switch is represented as a dvPortGroup on each vSphere Distributed Switch (VDS).
Logical switch dvPortGroup naming convention is vxw-dvs-###-virtualwire-###-sid-<Segment ID>-<Logical Switch Name>.
vxw: VXLAN-VirtualWire to distinguish the dvPortGroup created by NSX
dvs-###: MoRefID of the vDS
virtualwire-###: virtualwire ID within NSX
sid-<Segment ID>: segment ID or VNI
You can't create a same dvPortGroup name, it will throw an error
But you can create same Logical Switch name; the dvPortGroup name will be unique across different Logical Switches as the virtualwire ID & segment ID will be unique too
In your case the dvPortGroups name would be something like
vxw-dvs-74-virtualwire-1-sid-10046-MY_PRODUCTION_NETWORK
vxw-dvs-74-virtualwire-2-sid-10047-MY_PRODUCTION_NETWORK
vxw-dvs-74-virtualwire-3-sid-10048-MY_PRODUCTION_NETWORK
and so on
So I don't believe this is a bug
Hi Bayu,
Imagine the following situation, you've created a Logical Switch called 'MY_PRODUCTION_NETWORK' but others administrators created Logical Switches with the same name. Now you need to configure your Edge like in the following screenshot:
Which Logical Switch will you select? It's confusing at best.
I think this is a wrong behavior.
D.
Since they are using same name, you would want to connect to the correct VNI (Segment ID).
Logical Switch with same name is technically possible but yes I agree with you that the platform should not allow for a same name just like the vDS dvPortGroup.
You could probably file a feature request to VMware: Making a VMware feature request (1002123) | VMware KB
It makes a bit more sense when you think about it in a multi-tenant environment. Allowing tenants to have the same logical switch name means that they don't have to be aware of what other tenants are naming their logical switches. If you need to filter the responses, you can use the TenantID to reduce the scope of the results.