Q in VNI does not appear to be working. Nexus 9000

[ciscopower]

We are in the test phase for a deployment and are trying to get Q in VNI working over
a VXLAN fabric . When sending untagged traffic to the dotq tunnel interfaces we get connectivity between the hosts,.When sending a
802.1q tagged frame, the Leaf switches are not learning the MAC address and we
cannot get connectivity. We would expect the Fabric to learn MAC addresses form all
customer VLANs in this mode.

It appears as if traffic with an dot1q TAG is being dropped inbound in the Leaf Switch interfaces. I should mention that untagged traffic works as expected when the leaf port is in "dot1qtunnel" mode. We are using BGP to propagate the MAC addresses and this works as expected. When the leaf switch ports are in "trunk" mode  it also works as expected and MAC addresses are leaned on the appropriate VLAN.

Attached is a topology diagram. I am using a couple of catalyst switches at each end for testing.

The Leaf switch ports are configured as follows.

interface Ethernet1/1
switchport
switchport mode dot1q-tunnel
switchport access vlan 10
spanning-tree bpdufilter enable
mtu 9166
no shutdown

Based in this I would expect all traffic leaned on E1/1 to be added to the local MAC address table of the leaf with VLAN 10. As mentioned, this is only happening for untagged traffic. Based on the normal behaviour of dot1qtunnel I would also expect customer tagged traffic to be leaned against VLAN 10 and the innner TAG maintained.

Any assistance would be appreciated.

Regards

Phil

[Yves Louis · Accepted solution]

Hi Phil,

What are the leaf switches ?

2 slight comments.

1 - you need to configure the encapsulation with tag for the overlay (vxlan-with-tag),thus the original dot1Q tags will be kept inside the VXLAN encap

switch# config terminal
switch(config-if)# interface nve1
switch(config-if)# overlay-encapsulation vxlan-with-tag

2 - in your picture, you mentioned the VXLAN fab built with NFM in your picture - make sure that the above CLI are not removed after NFM synch's with its database.

[ciscopower]

I seem to have gotten to the bottom of the issue. It is configured correctly, however the following line from the latest release notes is incorrect, and the feature is not yet supported and will be supported on the EX line in Q4.

Thanks for your help.

■ Layer 2 Q-in-Q, due to a hardware limitation (supported for Cisco Nexus 93108TC-EX and 93180YC-EX switches

but not for Cisco Nexus 9200 Series switches)