You can on standard switch. two different hosts with their own standard switch. no problem having same name on network with same vlanid.
Host1:
Standardswitch (vswitch0):
Networkname: internalnetwork -> vlanid1
Host2:
Standardswitch (vswitch0):
Networkname: internalnetwork -> vlanid1
No problem vmotioning between host1 and host2. No need to redefine network on vmotion.
But if I create two distributed switches, i seem to need to have different names on the network.
Host1:
distributedswitch1 (uplinkports attached to host1):
Networkname: internalnetwork1 -> vlanid1
Host2:
Distributedswitch2(uplinkports attached to host2):
Networkname: internalnetwork2 -> vlanid1
Vmotion between host1 and host2 needs webclient and we need to redefine network src and dst, because it's different names.
Host1 and host2 is the example is in two different clusters. I understand that distributed switch can span over multiple hosts(that's why I want to use it), but I don't understand why naming can't be the same on two distributed switches. is it because a host can have two distributed switches attached on different uplinks? because if you got only got one distributed switch on one host and a different distributed switch on another one, I really can't understand why there is a limitation of naming.