Add drop reason/flags to individual flow entry
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 |
summary: |
- Better Diagnostics in Data plane + Add drop reason/flags to individual flow entry |
bug update...