NSX Guest inter vlan routing

[Marc PEREIRA]

Hello,

we're currently configuring NSX Guest inter vlan routing in our vCD/NSX environment to allow customer virtual firewall to use interface vlan tagging.

Configuration of parent and child port is OK following the documentation (https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/advanced-network-management/administration-guide/host-switches/configure-guest-inter-vlan-routing.html).

But when we shutdown the VM, it lose his parent port in the parent segment. And then, when we power it up back online, the VM attache itself to a brand new port in the parent segment... Breaking the childs context id configuration...

Have to reconfigure all the stuff...

Is there a solution to make a parent port persistent across VM power cycle ?

I also see that NSX dvport group in vSphere is configuring as ephemeral binding... Is there a way to configure it as static ? I looked in the NSX API Documentation but nothing found so far.

Here the environment information :

 - vCD : 10.6.1.24532667

 - NSX : 4.2.1.0.0.24304122

 - vSphere : 8.0.3.00400 (build 24322831)

Thanks for any help here

[Bogdan_Ionut]

No - today there is no supported way to make the NSX Guest Inter-VLAN Routing parent port persistent across VM power cycles. The behavior you are seeing is by design. 😀

When using NSX Guest Inter-VLAN Routing, the parent segment port is implemented as an NSX logical port backed by an ephemeral dvPort. On VM power-off, NSX deletes the logical port; on power-on, NSX creates a new port, with :a new logical port ID and new dvPort. Since child ports are bound to the parent port ID, the child context breaks.

As I mentioned, this is expected behavior in NSX 4.x.

The recommended approach is to avoid VM power-off operations or automate the reconfiguration of parent/child ports after power-on.