Mirrored packet dropped with Invalid NH on one of the ECMP mirror destination vrouter node with policy based mirroring

Bug #1720990 reported by alok kumar
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.2
New
High
Saurabh
R4.0
New
High
Saurabh
R4.1
New
High
Saurabh
R5.0
New
High
Saurabh
Trunk
New
High
Saurabh

Bug Description

With policy based mirroring with ECMP destinations, one of the destination vrouter drops packet with invalid NH.

Divakar is aware about the issue and has debugged it.

test scenario:
- 2 traffic VMs on nodec62
- mirror service instance with scaling, 2 mirror instances(v1)
- one mirror instance is on nodec62 and other on nodec12
- start ping between traffic VMs.
- invalid NH count on nodec12 keeps increasing without any packet sent to mirror instance.

Note: packet is mirrored on nodec62 mirror instance correctly when thats selected as the mirror destination.

root@nodec12:~# dropstats | grep -v " 0"

Flow Action Drop 31
Flow Unusable (Eviction) 2

Cloned Original 140586

Invalid NH 8573
Invalid Protocol 24

Duplicated 1

alok kumar (kalok)
tags: added: vrouter
removed: vr
Jeba Paulaiyan (jebap)
tags: added: releasenote
wenqing liang (wliang)
tags: added: sanityblocker
wenqing liang (wliang)
tags: added: sanity
removed: sanityblocker
wenqing liang (wliang)
tags: added: sanityblocker
removed: sanity
wenqing liang (wliang)
tags: added: sanity
removed: sanityblocker
tags: removed: sanity
Jeba Paulaiyan (jebap)
tags: added: releaseblocker
tags: removed: releasenote
Revision history for this message
Saurabh (sgupta84) wrote :

We have tested a workaround for the issue. Packet mode needs to be enabled on the mirrored VMI. Alok found this to be working as well. This has to be release noted for the release.

Jeba Paulaiyan (jebap)
tags: added: releasenotes
removed: releaseblocker
tags: added: releasenote
removed: releasenotes
Revision history for this message
Sivakumar Ganapathy (hotlava51) wrote :

This is a low priority bug at this point due to its minimal impact. Hence tracking this for 5.1.0.

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.