Native vlan ID in EX switches

I would like to show an example how we can use native vlan id in an EX switch. Normally if you set the port mode of an interface as trunk in EX switch, untagged traffic can’t pass through this interface. You have to tell Junos how it should behave on untagged frames.

This is my setup in which ge-0/0/0 port of an EX2200 is connected to an ESX server
I have untagged traffic to ESX server but tagged traffic to the VM cloud inside the host machine. I have two VLANs (101,103) for Virtual Machines inside this host. If I set the ge-0/0/0 as an access port, I can’t forward my frames tagged with these vlans. If I set it as trunk, I can’t reach ESX because it is an end host for my switch (though you can set vlan in ESX host interface, I am not doing for the demonstration purpose)

The config for EX switch for the port ge-0/0/0:

By the configuration statement “native-vlan-id default“, we instruct the switch to accept untagged frames. Our default vlan is really untagged? Let’s see:

As you can see although OSlab and vms vlans have tags 101,103, default vlan has no tag assigned which means any untagged frame received by this trunk interface will be in default vlan.

You have a feedback?