Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flow-capture and flow-fanout lost flows #17

Open
GoogleCodeExporter opened this issue Jun 23, 2015 · 0 comments
Open

flow-capture and flow-fanout lost flows #17

GoogleCodeExporter opened this issue Jun 23, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

flow-tools release: flow-tools-0.66

What steps will reproduce the problem?
1. start flow-fanout or flow-capture
/md/binarios/bin/netflow/flow-fanout 0/0/2056 0/0/2055 0/212.31.32.163/2055
/md/binarios/bin/netflow/flow-capture -z0 -N0 -V5 -n295 
-w/md/dumper/files/flow-capture 0/0/2055

2. the syslog shows:

May 20 12:20:55 dmdnet01 flow-fanout[4866]: ftpdu_seq_check(): 
src_ip=10.17.32.32 dst_ip=0.0.0.0 d_version=5 expecting=22030939 
received=3648399742 lost=3626368803
May 20 12:20:55 dmdnet01 flow-fanout[4866]: ftpdu_seq_check(): 
src_ip=10.17.32.32 dst_ip=0.0.0.0 d_version=5 expecting=3648400432 
received=3648400462 lost=30

What version of the product are you using? On what operating system?

HP-UX HP01 B.11.31 U ia64 4219704302 unlimited-user license


Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 20 May 2011 at 10:17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant