Details
-
Bug
-
Status: Resolved
-
Resolution: Duplicate
-
Carbon
-
None
-
None
-
Operating System: All
Platform: All
-
8321
Description
Using dovs I found the subsequent problem.
Table=223 has the following instructions:
table=223, n_packets=3, n_bytes=222, priority=260,nsp=52,tun_dst=172.19.0.2 actions=resubmit(,83)
table=223, n_packets=0, n_bytes=0, priority=250,nsp=52 actions=output:5
However, 172.19.0.2 is the VTEP of a different OVS. So packets hit that flow and then go to table 83 which does not exist because that OVS is not a SFF. The VTEP of the local OVS has the IP 172.19.0.3, so table=223 should be:
table=223, n_packets=3, n_bytes=222, priority=260,nsp=52,tun_dst=172.19.0.3 actions=resubmit(,83)
table=223, n_packets=0, n_bytes=0, priority=250,nsp=52 actions=output:5
Attachments
Issue Links
- duplicates
-
NETVIRT-631 Erroneous Egress Classifier flows causing packets to be egressed incorrectly
- Resolved