yahoo-eng-team team mailing list archive

[David Hill <1566951@xxxxxxxxxxxxxxxxxx>]

What needs to be documented here is that a SR-IOV port should only be
attached to the VM and not put in a DVR router as this will duplicate
the ports ... from my understanding of the issue.

Here is a simple representation of what should be configured:

VM -> SR-IOV VF -> SR-IOV PF -> Switch

and here is what you have configured when adding the SR-IOV port to the router:
VM \  -> SR-IOV VF -> SR-IOV PF -> Switch # port attached to the VM
    \ -> SR-IOV VF -> OVS -> SR-IOV-PF -> Switch # port also attached to the OVS router

... and that's what is duplicating the packets.   I guess here we could
:

1) Prevent attaching the SR-IOV port to a DVR router ...

I can't think of another possibility but it doesn't mean there're none.

** Also affects: neutron
   Importance: Undecided
       Status: New

** Changed in: neutron
       Status: New => Confirmed

** Changed in: mos/10.0.x
     Assignee: Alexander Adamov (aadamov) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1566951

Title:
  Duplicated traffic in SR-IOV and DVR mode

Status in Mirantis OpenStack:
  Won't Fix
Status in Mirantis OpenStack 10.0.x series:
  Confirmed
Status in neutron:
  Confirmed

Bug description:
  Detailed bug description:
   On DVR VLAN env vm with SR-IOV has duplicated traffic during pin external host or internal ip 

  Steps to reproduce:
  1. Deployed env with SR-IOV and DVR
  2. Create net1, subnet
  3. Create net2, subnet
  4. Create DVR router, set gatawey, add interface for both nets
  5. Create sr-iov port in net1 (port_sriov_1)
  6. Create sr-iov port in net2 (port_sriov_2)
  7. Boot ubuntu vm1 with port port_sriov_1
  8. Boot ubuntu vm 2with port port_sriov_2
  9. Associate floating for vm1
  10. Ping from vm1 8.8.8.8, ping vm2 by floating

  Expected results:
   Ping is available, packets are not duplicated

  Actual result:
  Packets are duplicated:
  ubuntu@vm-ew-1:~$ ping 10.1.2.6
  PING 10.1.2.6 (10.1.2.6) 56(84) bytes of data.
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.312 ms
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.313 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.313 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.313 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.314 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.314 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.314 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.315 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.315 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.315 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.316 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.316 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.316 ms (DUP!)

  ubuntu@vm-ew-1:~$ ping 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms (DUP!)
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms (DUP!)
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms (DUP!)
  64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=4.36 ms

  Description of the environment:
  Find on iso 155, vlan+dvr+enable sr-iov

  Additional information:
   I boot usual vm in net1 and ping 8.8.8.8 work good

To manage notifications about this bug go to:
https://bugs.launchpad.net/mos/+bug/1566951/+subscriptions