Mirroring : flow Stickiness issue when mirroring destination is in ECMP

Bug #1685768 reported by Hari Prasad Killi on 2017-04-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
Fix Committed
High
Divakar Dharanalakota

Bug Description

When the mirroring destination is ECMP, vRouter calculates the member of the ECMP group to which the packet should be sent to. If the members of the group change (mainly deletion, resulting in holes), vRouter does not ensure that the packets of the same flow go to the same mirror destination.

For the regular packets, flow stickiness is ensured with the help of the flows (ECMP index in the flows, more specifically). We could add mirror specific information in the original flow so that the same logic can be extended for mirror ECMPs too, thus achieving stickiness.

Jeba Paulaiyan (jebap) on 2017-04-24
Changed in juniperopenstack:
milestone: none → r4.0
description: updated
Hari Prasad Killi (haripk) wrote :

Alok tested this with CB-mainline build 54 and found the scenario to be working as desired. Closing the bug.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers