Technical Tip: Configuring an automation stitch to reboot downstream devices in the security fabric

If the device is in a security fabric, an automation stitch can only be configured in the root FortiGate.

The following is the configured script that reboots the devices added in the automation stitch on a weekly basis [every Sunday at 1 AM].

Follow these steps to create an automation stitch via the CLI that schedules reboots for downstream devices:

config system automation-stitch
    edit "Reboot-Test"
        set trigger "Reboot-Test"
            config actions                       

                edit 1
                    set action "Reboot FortiGate"
                    set required enable
                next
            end
        set destination "Reboot-Test"

    next
end

config system automation-trigger
    edit "Reboot-Test"
        set trigger-type scheduled
        set trigger-frequency weekly
        set trigger-weekday sunday
        set trigger-hour 13
    next
end

config system automation-action
    edit "Reboot FortiGate"
        set description "Reboot this FortiGate."
        set action-type system-actions
        set system-action reboot
        set minimum-interval 300
    next
end

To configure via the GUI, navigate to Security Fabric -> Automation on the root FortiGate and follow these steps:

1. Create an automation stitch and select the devices that need to reboot:

2. Create an automation trigger for rebooting devices:

3. Create an automation-action that reboots the devices:

Note: If any downstream device is scheduled for reboot or any time-based trigger/action is configured, the NTP status in downstream devices in security fabric or time zones needs to be the same as the root device in order to trigger it.

Related documents:
System automation actions to back up, reboot, or shut down the FortiGate - FortiGate 7.2.0 new features
Troubleshooting Tip: How to resolve an automation stitch which cannot be triggered