Add drop reason/flags to individual flow entry

Bug #1465891 reported by Sreelakshmi on 2015-06-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.20
Won't Fix
Medium
Anand H. Krishnan
R3.0
Fix Committed
Medium
Anand H. Krishnan
R3.1
Fix Committed
Medium
Anand H. Krishnan
Trunk
Fix Committed
Medium
Anand H. Krishnan

Bug Description

we have flow -l to check flow records but there is one instance during Singtel POC where flow -l shows "F" for a given flow but vRouter dropped it with "Invalid source" incrementing (in drop stats).

In this particular case, URFP check was failing due to which drop stats were incrementing & vRouter was dropping the packets while flow -l shows "F" for the flow in question.

Suggested improvements during debug session with Raja, Prasad and Nischal -
1. we should be able to correlate drop stats attribute to a given flow.
2. add a error code (32 bit for ex) to give a clue of why the flow error counters are incrementing.

In this particular case, URFP check was failing due to which drop stats were incrementing & vRouter was dropping the packets while flow -l shows "F" for the flow in question.

Thanks
Sree

Changed in juniperopenstack:
milestone: none → r2.21
tags: added: quench vrouter
information type: Proprietary → Public
Changed in juniperopenstack:
importance: Undecided → Medium
Nischal Sheth (nsheth) on 2015-07-15
summary: - Better Diagnostics in Data plane
+ Add drop reason/flags to individual flow entry

bug update...

Hari Prasad Killi (haripk) wrote :

commit 522013cfc53859f26d2b569350901be98644d831

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

Other bug subscribers