DPDK: Vrouter doesnot respond to arp req over subinterface

Bug #1628326 reported by Vinod Nair
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Won't Fix
High
Kiran
R3.0
Won't Fix
High
Kiran
R3.0.3.x
Won't Fix
High
Kiran
R3.1
Won't Fix
High
Kiran
R3.2
Won't Fix
High
Kiran
R4.0
Won't Fix
High
Kiran
R5.0
Won't Fix
High
Kiran
Trunk
Won't Fix
High
Kiran

Bug Description

With DPDK vrouter assigned with 1 CPU core , arp requests from Sub-interfaces are not being responded to . Regular interfaces is fine

If the dpdk vrouter is assigned 2 cores it is fine

The image has the fix for 1625896

There are no errors also in the logs

Version: 3.0.3.0-67~liberty

root@cs-scale-6:/var/crashes# vifdump 3 -nevv
tcpdump: WARNING: mon3: no IPv4 address assigned
tcpdump: listening on mon3, link-type EN10MB (Ethernet), capture size 65535 bytes
16:55:22.801958 02:55:1b:c4:06:ff > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 20, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.220.0.1 tell 10.220.0.220, length 28
16:55:23.401958 02:55:1b:c4:06:ff > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 20, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.220.0.1 tell 10.220.0.220, length 28
16:55:24.301959 02:55:1b:c4:06:ff > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 20, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.220.0.1 tell 10.220.0.220, length 28
16:55:25.101964 02:55:1b:c4:06:ff > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 20, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.220.0.1 tell 10.220.0.220, length 28
^C

root@cs-scale-6:/var/crashes# vif --list
Vrouter Interface Table

Flags: P=Policy, X=Cross Connect, S=Service Chain, Mr=Receive Mirror
       Mt=Transmit Mirror, Tc=Transmit Checksum Offload, L3=Layer 3, L2=Layer 2
       D=DHCP, Vp=Vhost Physical, Pr=Promiscuous, Vnt=Native Vlan Tagged
       Mnp=No MAC Proxy, Dpdk=DPDK PMD Interface, Rfl=Receive Filtering Offload, Mon=Interface is Monitored
       Uuf=Unknown Unicast Flood, Vof=VLAN insert/strip offload

vif0/0 PCI: 0000:00:00.0 (Speed 10000, Duplex 1)
            Type:Physical HWaddr:90:e2:ba:5a:8d:4c IPaddr:0
            Vrf:0 Flags:TcL3L2VpVof MTU:1514 Ref:12
            RX device packets:7871 bytes:1290858 errors:1
            RX port packets:7819 errors:0
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:7497 bytes:1193935 errors:0
            TX packets:4577 bytes:1397295 errors:0
            TX port packets:4568 errors:26
            TX device packets:5764 bytes:1586351 errors:0

vif0/1 Virtual: vhost0
            Type:Host HWaddr:90:e2:ba:5a:8d:4c IPaddr:0
            Vrf:0 Flags:L3L2 MTU:1514 Ref:7
            RX port packets:4572 errors:0
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:4572 bytes:1397181 errors:0
            TX packets:7497 bytes:1193935 errors:0
            TX port packets:7497 errors:0

vif0/2 Socket: unix
            Type:Agent HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:65535 Flags:L3 MTU:1514 Ref:3
            RX port packets:98 errors:0
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:98 bytes:8668 errors:0
            TX packets:2176 bytes:226370 errors:0
            TX queue packets:2176 errors:0
            TX port packets:2176 errors:0 syscalls:2176

vif0/3 PMD: tap46e90ced-c9
            Type:Virtual HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:1 Flags:PL3L2D MTU:9160 Ref:11
            RX port packets:48 errors:0 syscalls:1
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:48 bytes:2656 errors:0
            TX packets:30 bytes:1260 errors:0
            TX port packets:71 errors:19 syscalls:71

vif0/4 Virtual: Sub-VN-02-ru Vlan(o/i)(,S): 20/20 Bridge Index: 0 Parent:vif0/3
            Type:Virtual(Vlan) HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:3 Flags:PL3L2D MTU:1514 Ref:5
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:0 bytes:0 errors:0
            TX packets:30 bytes:1380 errors:0

vif0/5 Virtual: Sub-VN-01-ru Vlan(o/i)(,S): 10/10 Bridge Index: 0 Parent:vif0/3
            Type:Virtual(Vlan) HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:2 Flags:PL3L2D MTU:1514 Ref:5
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:0 bytes:0 errors:0
            TX packets:30 bytes:1380 errors:0

   root@cs-scale-6:/var/crashes# vif --list
Vrouter Interface Table

Flags: P=Policy, X=Cross Connect, S=Service Chain, Mr=Receive Mirror
       Mt=Transmit Mirror, Tc=Transmit Checksum Offload, L3=Layer 3, L2=Layer 2
       D=DHCP, Vp=Vhost Physical, Pr=Promiscuous, Vnt=Native Vlan Tagged
       Mnp=No MAC Proxy, Dpdk=DPDK PMD Interface, Rfl=Receive Filtering Offload, Mon=Interface is Monitored
       Uuf=Unknown Unicast Flood, Vof=VLAN insert/strip offload

vif0/0 PCI: 0000:00:00.0 (Speed 10000, Duplex 1)
            Type:Physical HWaddr:90:e2:ba:5a:8d:4c IPaddr:0
            Vrf:0 Flags:TcL3L2VpVof MTU:1514 Ref:12
            RX device packets:8362 bytes:1342150 errors:1
            RX port packets:8308 errors:0
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:7965 bytes:1239209 errors:0
            TX packets:4848 bytes:1446160 errors:0
            TX port packets:4839 errors:26
            TX device packets:6109 bytes:1646856 errors:0

vif0/1 Virtual: vhost0
            Type:Host HWaddr:90:e2:ba:5a:8d:4c IPaddr:0
            Vrf:0 Flags:L3L2 MTU:1514 Ref:7
            RX port packets:4843 errors:0
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:4843 bytes:1446046 errors:0
            TX packets:7965 bytes:1239209 errors:0
            TX port packets:7965 errors:0

vif0/2 Socket: unix
            Type:Agent HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:65535 Flags:L3 MTU:1514 Ref:3
            RX port packets:98 errors:0
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:98 bytes:8668 errors:0
            TX packets:2342 bytes:243634 errors:0
            TX queue packets:2342 errors:0
            TX port packets:2342 errors:0 syscalls:2344

vif0/3 PMD: tap46e90ced-c9
            Type:Virtual HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:1 Flags:PL3L2D MTU:9160 Ref:11
            RX port packets:90 errors:0 syscalls:1
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:90 bytes:4588 errors:0
            TX packets:30 bytes:1260 errors:0
            TX port packets:71 errors:19 syscalls:71

vif0/4 Virtual: Sub-VN-02-ru Vlan(o/i)(,S): 20/20 Bridge Index: 0 Parent:vif0/3
            Type:Virtual(Vlan) HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:3 Flags:PL3L2D MTU:1514 Ref:5
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:0 bytes:0 errors:0
            TX packets:30 bytes:1380 errors:0

vif0/5 Virtual: Sub-VN-01-ru Vlan(o/i)(,S): 10/10 Bridge Index: 0 Parent:vif0/3
            Type:Virtual(Vlan) HWaddr:00:00:5e:00:01:00 IPaddr:0
            Vrf:2 Flags:PL3L2D MTU:1514 Ref:5
            RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0
            RX packets:0 bytes:0 errors:0
            TX packets:30 bytes:1380 errors:0

root@cs-scale-6:/var/crashes# dropstats | grep -v " 0$"

Discards 3
Cloned Original 1838

Invalid Packets 2

root@cs-scale-6:/var/crashes# dropstats | grep -v " 0$"

Discards 3
Cloned Original 1844

Invalid Packets 2

root@cs-scale-6:/var/crashes# rt --dump 3 --family inet | grep 10.220.0.220
10.220.0.220/32 32 PT - 26 2:55:1b:c4:6:ff(56620)

root@cs-scale-6:/var/crashes#
root@cs-scale-6:/var/crashes# nh --get 26
Id:26 Type:Encap Fmly: AF_INET Rid:0 Ref_cnt:4 Vrf:3
              Flags:Valid, Policy,
              EncapFmly:0806 Oif:4 Len:18
              Encap Data: 02 55 1b c4 06 ff 00 00 5e 00 01 00 81 00 00 14 08 00

Vinod Nair (vinodnair)
information type: Proprietary → Public
Revision history for this message
Raja Sivaramakrishnan (raja-u) wrote :

Release Note: DPDK-based compute node may not handle ARP packets correctly if only one CPU core is assigned to vrouter in the testbed file

Vineet Gupta (vineetrf)
tags: added: releasenote
Jeba Paulaiyan (jebap)
Changed in juniperopenstack:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.