Yes, the same network can exist in both port groups so the real issue is where the default gateway for VMs connected to either port group lives. Migration strategies for this are covered in detail in the VMware® NSX-v Brownfield Design and Deployment Guide - ver 1.2 but typically you'll use the L2 bridging functionality in NSX to connect your DPG_WEB and LS_WEB L2 domains so that VMs in either port group can connect to the default gateway regardless of whether it's the legacy physical network based gateway or the new NSX based (probably on the DLR) gateway.
Yep, as lhoffer mentioned, L2 bridging can achieve what you are describing. Just keep in mind that you should not use the DLR as the default gateway for any logical switches that are bridged. You'll likely run into problems with the VLAN backed machines.
MikeMy blog: https://vswitchzero.com1 person found this helpful
Follow me on Twitter: @vswitchzero
Ohh i see. So i can have 2 scenarios:
- Migrate all PG_WEB to NSX and use the DLR as the gateway of my network segment. So, the PG_WEB network won't exist anymore in my physical enviroment. And if i want to reached it on NSX it should be through my DLR-EDGE architecture..
- Partially migrate the PG_WEB workload, and in this case i need to use L2 bridging to make my workload in NSX and my workload in my physical VLAN talk. And then i have to choose whether they will use the physical gateway or the DLR gateway ( and as Mike suggested, use the physical gateway!).
Ok, now i feel that i have everything cleared up!
Thank you very much!