Probe Failed Error

Yep sometimes the error handling in FortiManager is very unhelpful. Probe failed can mean a lot of things.

- the interface on the FGT you use to add the FGT to the Manager doesn't have FGFM Protocoll enabled.

- I also had cases were I got this when more than one interface on the FGT had FGFM enabled.

- you are missing routing and/or policies so the Manager cannot reach the Fortigate

- ... there is more reasons but I don't currently remember.

you could open a cli on FGT and  run the FGFM debug log:

diag debug application fgfm 255

diag debug enable

(not sure if it was fgfm or fgfmd but xou could write fgf and use tab-completion though)

Then try to add the FGT to FMG again and look at the log.

Unfortunately it is rather annyoing to debug the FMG Side that way if you have more FGT in there because that is causing loads of FGFM Traffic then...

hth

Sebastian

you could set the local certificate that the FGT uses. For whtever reason on the FGT itself this can only be done on CLI:

config system central-management
set local-cert ''
end

Also i often have issues with the FGT not beeing able to autoselect the correct interface. In this case the option "set fmg-source-ip <ipofinterface>"  (also not availabe in FGT Gui) helped me.

Dear Douglas Adams, 

Thank you for your support. But nothing worked fine.

Regards,

Aneeq Ahmed