Fortinet white logo
Fortinet white logo

SD-WAN / SD-Branch Architecture for MSSPs

ZTP using DHCP option

ZTP using DHCP option

With the DHCP option, FortiCloud connectivity is not required:

  • A new FortiGate device with a factory-default configuration is plugged in and powered on.

  • FortiGate boots up and obtains its WAN connectivity from a DHCP server.

  • The same DHCP server also provides the location of FortiManager, using DHCP Option 240/241.

  • Finally, the FortiGate device connects to FortiManager, authenticates using its own serial number, and triggers the Auto-Link process.

This method is well-suited for corporate environments, where on-site network infrastructure is under your control. Therefore, it is possible to apply custom configuration to the local DHCP server, adding the FortiManager location.

As can be seen, this method requires neither initial configuration nor any additional human intervention, once the on-site infrastructure is properly configured.

ZTP using DHCP option

ZTP using DHCP option

With the DHCP option, FortiCloud connectivity is not required:

  • A new FortiGate device with a factory-default configuration is plugged in and powered on.

  • FortiGate boots up and obtains its WAN connectivity from a DHCP server.

  • The same DHCP server also provides the location of FortiManager, using DHCP Option 240/241.

  • Finally, the FortiGate device connects to FortiManager, authenticates using its own serial number, and triggers the Auto-Link process.

This method is well-suited for corporate environments, where on-site network infrastructure is under your control. Therefore, it is possible to apply custom configuration to the local DHCP server, adding the FortiManager location.

As can be seen, this method requires neither initial configuration nor any additional human intervention, once the on-site infrastructure is properly configured.