The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.
Bug 1728318 - ping loss of first packet with OVN l3 logical router. when using VLAN tenant network type
Summary: ping loss of first packet with OVN l3 logical router. when using VLAN tenan...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux Fast Datapath
Classification: Red Hat
Component: ovn2.11
Version: RHEL 8.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: lorenzo bianconi
QA Contact: haidong li
URL:
Whiteboard:
Depends On: 1600115 1701893 1728674
Blocks: 1637466
TreeView+ depends on / blocked
 
Reported: 2019-07-09 16:42 UTC by lorenzo bianconi
Modified: 2020-01-14 20:32 UTC (History)
24 users (show)

Fixed In Version: ovn2.11-2.11.0-24.el7fdn
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1701893
Environment:
Last Closed: 2019-08-20 11:05:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2527 0 None None None 2019-08-20 11:05:20 UTC

Comment 2 haidong li 2019-07-23 01:34:06 UTC
Hi Lorenzo,
   I can't get exactly how to setup the vlan tenant network.Is it simply adding the command below to these steps to make all the external traffic have vlan tags?  If not please help explain how to establish the vlan tenant network,thanks!

"ovn-nbctl set logical_switch_port ln-s3 options:network_name=tagtest tag_request=4"

steps:
1. boot new vm on ovn setup 
2. add to him FIP 
3. ping from the external network to the vm you see that the first packet is lost.

Comment 3 haidong li 2019-08-05 08:08:47 UTC
No issue found on the latest version:
[root@dell-per730-19 ovn]# uname -a
Linux dell-per730-19.rhts.eng.pek2.redhat.com 3.10.0-1061.el7.x86_64 #1 SMP Thu Jul 11 21:02:44 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@dell-per730-19 ovn]# rpm -qa | grep openvswitch
kernel-kernel-networking-openvswitch-ovn-1.0-130.noarch
openvswitch-selinux-extra-policy-1.0-13.el7fdp.noarch
openvswitch2.11-2.11.0-18.el7fdp.x86_64
[root@dell-per730-19 ovn]# rpm -qa | grep ovn
kernel-kernel-networking-openvswitch-ovn-1.0-130.noarch
ovn2.11-central-2.11.0-26.el7fdp.x86_64
ovn2.11-2.11.0-26.el7fdp.x86_64
ovn2.11-host-2.11.0-26.el7fdp.x86_64
[root@dell-per730-19 ovn]#
[root@dell-per730-19 ovn]# ovn-nbctl show
switch 1d735dfc-9ab6-4440-9f74-9e369b671b33 (s2)
    port hv1_vm00_vnet1
        addresses: ["00:de:ad:01:00:01 172.16.102.11"]
    port s2_r1
        type: router
        addresses: ["00:de:ad:ff:01:02 172.16.102.1"]
        router-port: r1_s2
    port hv1_vm01_vnet1
        addresses: ["00:de:ad:01:01:01 172.16.102.12"]
switch f03fc638-5f98-4b67-8aa7-5de0cb1150d5 (public)
    port ln_p1
        type: localnet
        tag: 3
        addresses: ["unknown"]
    port public_r1
        type: router
        router-port: r1_public
switch 50907f4e-7de8-4711-9d67-005403aa973b (s3)
    port hv0_vm01_vnet1
        addresses: ["00:de:ad:00:01:01 172.16.103.12"]
    port s3_r1
        type: router
        addresses: ["00:de:ad:ff:01:03 172.16.103.1"]
        router-port: r1_s3
    port hv0_vm00_vnet1
        addresses: ["00:de:ad:00:00:01 172.16.103.11"]
router 3058d52b-bdf3-40c9-9dcf-fe068fd35380 (r1)
    port r1_public
        mac: "40:44:00:00:00:03"
        networks: ["172.16.104.1/24"]
    port r1_s2
        mac: "00:de:ad:ff:01:02"
        networks: ["172.16.102.1/24"]
    port r1_s3
        mac: "00:de:ad:ff:01:03"
        networks: ["172.16.103.1/24"]
    nat 2c5aff4e-5305-4716-b8d3-f94c108f292c
        external ip: "172.16.104.201"
        logical ip: "172.16.103.11"
        type: "dnat_and_snat"
    nat 98b35136-0a42-4a9d-ac37-5bb10b2d9d66
        external ip: "172.16.104.200"
        logical ip: "172.16.102.11"
        type: "dnat_and_snat"

[root@localhost ~]# ping 172.16.104.200
PING 172.16.104.200 (172.16.104.200) 56(84) bytes of data.
64 bytes from 172.16.104.200: icmp_seq=1 ttl=63 time=1.73 ms
64 bytes from 172.16.104.200: icmp_seq=2 ttl=63 time=0.379 ms
64 bytes from 172.16.104.200: icmp_seq=3 ttl=63 time=0.353 ms
64 bytes from 172.16.104.200: icmp_seq=4 ttl=63 time=0.350 ms
64 bytes from 172.16.104.200: icmp_seq=5 ttl=63 time=0.369 ms
64 bytes from 172.16.104.200: icmp_seq=6 ttl=63 time=0.357 ms

--- 172.16.104.200 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5001ms
rtt min/avg/max/mdev = 0.350/0.591/1.738/0.513 ms
[root@localhost ~]# 


[root@dell-per730-19 ovn]# tcpdump -ei p4p2 -nn | grep 172.16
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on p4p2, link-type EN10MB (Ethernet), capture size 262144 bytes
04:06:20.280517 00:00:00:04:05:06 > 00:00:00:01:02:03, ethertype 802.1Q (0x8100), length 102: vlan 3, p 0, ethertype IPv4, 172.16.104.201 > 172.16.104.200: ICMP echo request, id 11141, seq 1, length 64
04:06:20.281523 00:00:00:01:02:03 > 00:00:00:04:05:06, ethertype 802.1Q (0x8100), length 102: vlan 3, p 0, ethertype IPv4, 172.16.104.200 > 172.16.104.201: ICMP echo reply, id 11141, seq 1, length 64
04:06:21.281600 00:00:00:04:05:06 > 00:00:00:01:02:03, ethertype 802.1Q (0x8100), length 102: vlan 3, p 0, ethertype IPv4, 172.16.104.201 > 172.16.104.200: ICMP echo request, id 11141, seq 2, length 64
04:06:21.281832 00:00:00:01:02:03 > 00:00:00:04:05:06, ethertype 802.1Q (0x8100), length 102: vlan 3, p 0, ethertype IPv4, 172.16.104.200 > 172.16.104.201: ICMP echo reply, id 11141, seq 2, length 64
04:06:22.281598 00:00:00:04:05:06 > 00:00:00:01:02:03, ethertype 802.1Q (0x8100), length 102: vlan 3, p 0, ethertype IPv4, 172.16.104.201 > 172.16.104.200: ICMP echo request, id 11141, seq 3, length 64
04:06:22.281817 00:00:00:01:02:03 > 00:00:00:04:05:06, ethertype 802.1Q (0x8100), length 102: vlan 3, p 0, ethertype IPv4, 172.16.104.200 > 172.16.104.201: ICMP echo reply, id 11141, seq 3, length 64
^C38 packets captured
38 packets received by filter
0 packets dropped by kernel

Comment 5 errata-xmlrpc 2019-08-20 11:05:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2527


Note You need to log in before you can comment on or make changes to this bug.