Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • Administration Guide

    Home FortiManager 7.6.0 Administration Guide
    7.6.0
    7.6.1
    7.6.0
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    7.2.8
    7.2.7
    7.2.6
    7.2.5
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.0.13
    7.0.12
    7.0.11
    7.0.10
    7.0.9
    7.0.8
    7.0.7
    7.0.6
    7.0.5
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.15
    6.4.14
    6.4.13
    6.4.12
    6.4.11
    6.4.10
    6.4.9
    6.4.8
    6.4.7
    6.4.6
    6.4.5
    6.4.4
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.2.13
    6.2.12
    6.2.11
    6.2.10
    6.2.9
    6.2.8
    6.2.7
    6.2.6
    6.2.6
    6.2.5
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.0.12
    6.0.11
    6.0.10
    6.0.9
    6.0.8
    6.0.7
    6.0.6
    6.0.5
    6.0.4
    6.0.3
    6.0.2
    6.0.1
    6.0.0
    5.6.11
    5.6.10
    5.6.9
    5.6.8
    5.6.7
    5.6.6
    5.6.5
    5.6.4
    5.6.3
    5.6.2
    5.6.1
    5.6.0
    5.4.7
    5.4.6
    5.4.5
    5.4.4
    5.4.3
    5.4.2
    5.4.1
    5.4.0
    5.2.10
    5.2.7
    5.2.6
    5.2.4
    5.2.3
    5.2.2
    5.2.1
    5.2.0
    5.0.12
    5.0.11
    5.0.10
    5.0.9
    5.0.8
    5.0.7
    5.0.6
    5.0.5
    5.0.4
    5.0.3
    5.0.2
    4.3.8
    4.3.7
    4.3.6
    4.3.5
    4.3.4
    4.3.3
    4.3.2
    4.3.1
    4.3.0
    4.2.9
    4.2.8
    4.2.7
    4.2.6
    4.2.5
    4.2.4
    4.2.3
    4.2.2
    4.2.1
    4.2.0
    4.1.0
    4.0.3
    4.0.2
    4.0.1
    4.0.0

    Onboarding new branch devices

    Onboarding new branch devices

    The SD-WAN overlay template uses one or more device groups to determine which devices receive the SD-WAN provisioning templates.

    When a new device is added to a device group specified in the SD-WAN overlay template, the SD-WAN provisioning templates are automatically assigned to the device, and you can install the changes using the Install Wizard.

    Branch onboarding can be further simplified with the use of device blueprints and metadata variables:

    • Device blueprints can be used when adding model devices to FortiManager to simplify configuration of device settings, including device groups, configuring pre-run templates, policy packages, provisioning templates, and more. See Using device blueprints for model devices.

    • Metadata variables can be used as variables in provisioning templates. The branch_id variable is automatically created by the template and each branch device must be assigned a unique value. A branch ID value can be automatically assigned to devices in the SD-WAN branch device group when the Automatic Branch ID Assignment setting is enabled in the SD-WAN overlay template wizard. See ADOM-level metadata variables.

    When onboarding multiple new branch devices, you can import devices from a CSV file using device blueprints. Metadata fields including the branch_id variable can be specified directly in the CSV file. See Import model devices from a CSV file.

    To onboard new branch devices:

    1. Add the new FortiGate model device to FortiManager using the Device Manager.
      Optionally, you can configure a device blueprint to simplify device onboarding. See Using device blueprints for model devices.

    2. Assign the FortiGate device to the template's branch device group.
      The branch provisioning templates are automatically assigned to the device.

    3. Specify the metadata variables used by the SD-WAN overlay template. By default, the branch_id metadata variable must be specified. When Automatic Branch ID Assignment setting is enabled in the wizard, the branch ID is automatically applied to devices in the branch device group. See Automatic Branch ID Assignment.

    4. Assign policy package for the branch device, and then install the changes using the Install Wizard. See Install wizard.

    Previous
    Next

    Onboarding new branch devices

    Onboarding new branch devices

    The SD-WAN overlay template uses one or more device groups to determine which devices receive the SD-WAN provisioning templates.

    When a new device is added to a device group specified in the SD-WAN overlay template, the SD-WAN provisioning templates are automatically assigned to the device, and you can install the changes using the Install Wizard.

    Branch onboarding can be further simplified with the use of device blueprints and metadata variables:

    • Device blueprints can be used when adding model devices to FortiManager to simplify configuration of device settings, including device groups, configuring pre-run templates, policy packages, provisioning templates, and more. See Using device blueprints for model devices.

    • Metadata variables can be used as variables in provisioning templates. The branch_id variable is automatically created by the template and each branch device must be assigned a unique value. A branch ID value can be automatically assigned to devices in the SD-WAN branch device group when the Automatic Branch ID Assignment setting is enabled in the SD-WAN overlay template wizard. See ADOM-level metadata variables.

    When onboarding multiple new branch devices, you can import devices from a CSV file using device blueprints. Metadata fields including the branch_id variable can be specified directly in the CSV file. See Import model devices from a CSV file.

    To onboard new branch devices:

    1. Add the new FortiGate model device to FortiManager using the Device Manager.
      Optionally, you can configure a device blueprint to simplify device onboarding. See Using device blueprints for model devices.

    2. Assign the FortiGate device to the template's branch device group.
      The branch provisioning templates are automatically assigned to the device.

    3. Specify the metadata variables used by the SD-WAN overlay template. By default, the branch_id metadata variable must be specified. When Automatic Branch ID Assignment setting is enabled in the wizard, the branch ID is automatically applied to devices in the branch device group. See Automatic Branch ID Assignment.

    4. Assign policy package for the branch device, and then install the changes using the Install Wizard. See Install wizard.

    Previous
    Next