I am trying to reboot a downstream device in the fabric, but the
automation stitch is not triggering. The trigger is a weekly schedule at
hour 3 (3am - see image below). For action, I've tried using the system
action (included with v7.2 onward) as we...
I currently have event triggers working on the FortiGate to ban IP's
when the event handler on the FortiAnalyzer sees a matching event from
the FortiGate. I also have an alert working within FortiAnalyzer for
FortiMail when the event handler sees a m...
Yes, the time zone (or just the time possibly) have to match. When
trying with the root set to America/Toronto and the downstream set to
America/Vancouver it would not trigger via the schedule. When we set the
downstream to America/Toronto, it worked...
Working with TAC, we determined the issue was related to the time zone
setting (System > System > Time zone). For the automation stitch to
work, the downstream FortiGate time had to match the root. So even if
your root FortiGate is in Toronto (GMT-5)...
To clarify, the downstream device is selected. Recall, when using the
system action and clicking on the Test Automation Stitch, it reboots the
downstream device. I've opened a ticket with TAC.
Here is the latest from support:..."Looks like this ZSTD is implemented
in FortiOS for other uses, but not for inspection. This means that the
inspection profiles applied to a policy that is supposed to allow the
zstd-encypted sites will fail and the...
