Debug Command isn' t work [fixed]

[#1]

I had a FW 3016B and since yesterday all the debug command are not working, i had probe: FG-3016B # diagnose debug enable FG-3016B # diagnose debug application ike 2 FG-3016B # FG-3016B # FG-3016B # FG-3016B # FG-3016B # diagnose debug info debug output: enable console timestamp: enable ike debug level: 2 with no filter CLI debug level: 3 FG-3016B # FG-3016B # diagnose de flow show show trace messages on console show function name FG-3016B # diag deb flow filter dport 80 FG-3016B # dia deb info debug output: enable console timestamp: enable CLI debug level: 3 FG-3016B # diag deb flo tra start FG-3016B # After this command the FW don' t show anything Fortigate-3016B 3.00-b5419(MR7) And this had 2 VDOM configure Somebody helpme?

[red_adair]

The Debug commands are not documented and not " official" , hence they may change in Syntax. Not sure when the Level changed but at least in 4.1 you have to use " -1" #diag debug ena # diag debug app ike -1 Optionally set a filter before: # diag vpn ike filter ------------ I think for diag debug flow you have to enter the number of capture packets, like: # diag debug ena # <.....> # diag debug flow trace start 200 -R.

[#3]

that it' s the problem i trying any diagnose debug command and don' t work This doesn' t give me any information =/

[abelio]

Valeria, no one option of ' diagnose debug' command is working for you? i.e ' diagnose debug rating' doesn' t prints anything at all? ' diagnose debug crashlog read' shows something useful? If so, the more simpler conclusion would be to consider that some daemon is dead; Rebooting the unit and retry is an option for you?

[#5]

FG-3016B # diagnose debug rating Locale : english License : Contract Expiration : Sat Nov 10 21:00:00 2012 Hostname : service.fortiguard.net -=- Server List (Mon Feb 15 11:06:06 2010) -=- IP Weight RTT Flags TZ Packets Curr Lost Total Lost 216.156.209.26 0 0 D 0 0 0 0 208.91.112.194 5 0 DI 0 2 2 2 82.71.226.65 5 0 D 0 1 1 1 i really don' t understand what' s mean all this =/ I can' t reboot so easily this FGT....

[#6]

I open a case in Fortinet and they give me this command diag debug reset diag debug en diagnose debug application ike 255 and now this it' s working! the why it' s still a mistery