Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Problem with the debug flow
Hello,
i have a problem, when I enable the debugging(flow) I can not display any messages, why?
debug output: enable
console timestamp: enable
diag debug flow show console: enable
Thanks
10 REPLIES 10
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This commands are right, but you' ve missed in manual other.
diag debug flow trace start X
where X in number of packets I think
with
diag debug flow filter ........... you can limit traffic to flow debug by IPs, ports etc.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
but also with the numbers it does not work....
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
perhaps start with
diag debug enable
to show output on console
and
diag debug flow show console enable
diag debug flow show funct enable
cheers, Eric
Rackmount your Fortinet --> http://www.rackmount.it/fortirack
Rackmount your Fortinet --> http://www.rackmount.it/fortirack
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is the same.....don' t work :(
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you accidentally set a filter ?
# diag debug flow filter
It also doesn' t show Traffic that is offloaded to a NP2/NP4/SoC Network Processor.
Only (eg in TCP) the initial Handhshake should be seen.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, i can' t view nothing...
I view only with the " diagnose sniffer"
is it possible that debugging is written to the flash?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
nope,
please post the output of diag debug flow filter
perhaps your filter is wrong
the std procedure for deb flow is:
dia debug enable
dia deb flow show console enable
dia deb flow show funct enable
dia deb flow filter <filters>
dia deb flow trace start <no of packets>
Rackmount your Fortinet --> http://www.rackmount.it/fortirack
Rackmount your Fortinet --> http://www.rackmount.it/fortirack
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes i know,
diagnose debug flow filter
vf: any
proto: any
Host addr: any
Host saddr: any
Host daddr: any
port: any
sport: any
dport: any
sorry but don' t work...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do You have MR3? And a box bis NP2 asic?
I' ve seen a similar behavior with a FG200B. I see traffic with " diag sniffer packet..." , but don' t see a session with " diag debug flow" .