R4.1 build 15 Netronome 47: Gwless forwarding not working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
New
|
Medium
|
Pieter Malan | ||
R4.1 |
Won't Fix
|
Medium
|
Pieter Malan | ||
Trunk |
Won't Fix
|
Medium
|
Pieter Malan |
Bug Description
Seeing the issue on Netronome testbed with acceleration enabled. Without acceleration, the issue is not observed.
Steps to recreate the issue:
1) Create a VN vn1
2) enable ip fabric forwarding in vn1
Subnet(s)
CIDR Gateway Service Address DNS DHCP Allocation Pools
30.238.247.0/24 30.238.247.1 30.238.247.2 Enabled Enabled -
IP Fabric Forwarding Enabled
2) Launch 2 VMs in VN1
Ping from vm1 to vm2 and expect ping to work.
Observations:
1) Ping not working when gwless (ip fabric forwarding ) and netronome acceleration is enabled
^C
--- 30.238.247.5 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
$ ifconfig
eth0 Link encap:Ethernet HWaddr 02:04:F9:A4:C9:3B
inet addr:30.238.247.6 Bcast:30.
inet6 addr: fe80::4:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:924 errors:0 dropped:0 overruns:0 frame:0
TX packets:962 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:87628 (85.5 KiB) TX bytes:92650 (90.4 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
$ ping 30.238.247.5
PING 30.238.247.5 (30.238.247.5): 56 data bytes
2) Ping starts working on disabling ip fabric forwarding ( Netronome acceleration is still enabled)
$ ping 30.238.247.5
PING 30.238.247.5 (30.238.247.5): 56 data bytes
64 bytes from 30.238.247.5: seq=0 ttl=63 time=1.622 ms
64 bytes from 30.238.247.5: seq=1 ttl=63 time=0.248 ms
64 bytes from 30.238.247.5: seq=2 ttl=63 time=0.283 ms
64 bytes from 30.238.247.5: seq=3 ttl=63 time=0.242 ms
64 bytes from 30.238.247.5: seq=4 ttl=63 time=0.243 ms
^C
--- 30.238.247.5 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.242/0.527/1.622 ms
$
3) Ping works on disabling Netronome acceleration ( ip fabric forwarding is still enabled)
TEST : test_gw_
Test Gateway less forwarding with single VN and IP Fabric provider
over vn1. Multiple VMs will be launched across compute nodes
and ping between VMs should be successful and happen through
through underlay. Also, ping between VMs to vhosts also should be
2018-10-11 10:08:25,562 - INFO - Created BGP router: hooper
n2018-10-11 10:08:25,959 - INFO - Using existing project [u'default-domain', u'ctest-
2018-10-11 10:08:25,962 - INFO - Default SG to be edited for allow all on project: ctest-TestGWLes
2018-10-11 10:08:26,037 - INFO - Adding rules to the default security group in Project ctest-TestGWLes
> /contrail-
-> vn_fixtures = self.setup_vns(vn)
2018-10-11 10:08:28,366 - INFO - Created VN vn1
2018-10-11 10:08:28,656 - INFO - Configuring IP Fabric forwarding on VN: vn1
11 10:08:33,292 - INFO - VMI 6b67ae72-
2018-10-11 10:08:35,759 - INFO - VM ([<Server: ctest-TestGWLes
2018-10-11 10:08:37,729 - INFO - VMI 04f9a4c9-
2018-10-11 10:08:41,565 - INFO - VM ([<Server: ctest-TestGWLes
2018-10-11 10:08:41,567 - INFO - Waiting for VM ctest-TestGWLes
2018-10-11 10:08:55,864 - INFO - Ping to Metadata IP 169.254.0.3 of VM ctest-TestGWLes
2018-10-11 10:09:01,067 - INFO - Waiting for VM ctest-TestGWLes
2018-10-11 10:09:03,992 - INFO - Ping to Metadata IP 169.254.0.7 of VM ctest-TestGWLes
--Return--
> /contrail-
2018-10-11 10:14:23,074 - INFO - Route: 30.238.247.6 is found in default routing instance as expected in agent on compute node: 192.168.11.169
2018-10-11 10:14:23,165 - INFO - Route: 30.238.247.5 is found in default routing instance as expected in agent on compute node: 192.168.11.164
2018-10-11 10:14:23,474 - INFO - Route: 30.238.247.6 is found in defaultrouting instance as expected incontrol node: 192.168.31.4
2018-10-11 10:14:23,724 - INFO - Route: 30.238.247.5 is found in defaultrouting instance as expected incontrol node: 192.168.31.4
[cirros@
[cirros@
[cirros@
[cirros@
[cirros@
[cirros@
Warning: sudo() received nonzero return code 1 while executing 'ping -s 56 -c 2 -W 1 30.238.247.5'!
2018-10-11 10:14:28,020 - WARNING - Ping to IP 30.238.247.5 from VM ctest-TestGWLes
[cirros@
[cirros@
[cirros@
[cirros@
[cirros@
[cirros@
description: | updated |
description: | updated |
Changed in juniperopenstack: | |
importance: | Undecided → Critical |
tags: |
added: blocker removed: vrouter |
tags: | added: releasenote |
We saw that VRCNTR_ WIRE_DROP_ INVALID_ VIF gets incremented for packets arriving over the wire. The source side seems to be operating as expected. It is on the destination side where the packets are dropped.
INVALID_VIF gets incremented when the input_vif_index == -1, further investigation is required to determine why the input_vif_index is -1.