Comment 1 for bug 1786487

Updating the findings based on debugging with Shashi just now.

1) When encap type is VXLAN, the mirrored pkt is reaching the compute node of the analyser vm but not reaching the analyser VM.

23:11:34.579559 0c:c4:7a:dc:44:6b > 0c:c4:7a:dc:42:d7, ethertype IPv4 (0x0800), length 216: 10.10.11.5.54784 > 10.10.11.19.4789: VXLAN, flags [I] (0x08), vni 7
02:5c:95:74:c5:e5 > 00:00:5e:00:01:00, ethertype IPv4 (0x0800), length 166: 2.168.119.3.ssh > 2.168.119.2.60988: Flags [P.], seq 800:900, ack 1, win 588, options [nop,nop,TS val 111106 ecr 41912808], length 100
23:11:35.578872 0c:c4:7a:dc:44:6b > 0c:c4:7a:dc:42:d7, ethertype IPv4 (0x0800), length 148: 10.10.11.5.59136 > 10.10.11.19.4789: VXLAN, flags [I] (0x08), vni 7
02:5c:95:74:c5:e5 > 00:00:5e:00:01:00, ethertype IPv4 (0x0800), length 98: 2.168.119.3 > 89.239.240.3: ICMP echo request, id 2854, seq 55, length 64

Looking at the L2 table, I don’t see a proper NH for the pkt to be sent to the analyser VM.
I am not sure if the dest mac highlighted above should be the analyser VM’s mac for L2 lookup to succeed.

2) It works fine when the encap type is changed to MPLSoUDP. This is because the pkt is sent with correct label 36 which corresponds to the analyser VM tap interface. Hence the mirrored pkts are able to reach the analyser VM.

We need to analyse more why it is not working with VXLAN encap.