Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

Administration Guide

Static route templates

You can provision static routes to FortiGate devices by using a static route template.

When creating static routes for IPv4 and subnets, you can use meta field variables for objects of type device VDOM. See Meta Fields.

To create a new static route template:
  1. Go to Device Manager > Provisioning Templates > Static Route Templates.

  2. Create a static route template:
    1. In the toolbar, click Create New. The Create New Route Template dialog box appears.
    2. In the Name box, type a name for the template, and click OK. The new template is created.

  3. Open the template for editing, and create a static route:
    1. In the content pane, double-click the template. The template opens for editing.

    2. In the toolbar, click Create New. The Create New Static Route pane is displayed.

      You can use meta field variables created for an object type of Device VDOM when creating IPv4 static routes for subnets. In the following example, variable $(vdom-ip) is used:

    3. Complete the following options, and click OK.

      Type

      Select the type of static route. Choose between IPv4 and IPv6.

      Destination

      Select the destination for the route. Choose between Subnet, Internet Service, and Internet Service Custom.

      When you select Type of IPv4 and Destination of Subnet, you can use a meta field variable for the subnet. The input format is $(meta_field_name).

      If not using a meta field variable, specify the subnet.

      Gateway Address

      Specify the IP address for the gateway.

      Interface

      Specify the interface.

      Comments

      (Optional) Type a comment about the static route.

      Advanced Options

      Expand to display advanced options.

      The static route is created.

  4. Assign the template of static routes to one or more devices or device groups.
  5. Install the configuration to devices.

Static route templates

You can provision static routes to FortiGate devices by using a static route template.

When creating static routes for IPv4 and subnets, you can use meta field variables for objects of type device VDOM. See Meta Fields.

To create a new static route template:
  1. Go to Device Manager > Provisioning Templates > Static Route Templates.

  2. Create a static route template:
    1. In the toolbar, click Create New. The Create New Route Template dialog box appears.
    2. In the Name box, type a name for the template, and click OK. The new template is created.

  3. Open the template for editing, and create a static route:
    1. In the content pane, double-click the template. The template opens for editing.

    2. In the toolbar, click Create New. The Create New Static Route pane is displayed.

      You can use meta field variables created for an object type of Device VDOM when creating IPv4 static routes for subnets. In the following example, variable $(vdom-ip) is used:

    3. Complete the following options, and click OK.

      Type

      Select the type of static route. Choose between IPv4 and IPv6.

      Destination

      Select the destination for the route. Choose between Subnet, Internet Service, and Internet Service Custom.

      When you select Type of IPv4 and Destination of Subnet, you can use a meta field variable for the subnet. The input format is $(meta_field_name).

      If not using a meta field variable, specify the subnet.

      Gateway Address

      Specify the IP address for the gateway.

      Interface

      Specify the interface.

      Comments

      (Optional) Type a comment about the static route.

      Advanced Options

      Expand to display advanced options.

      The static route is created.

  4. Assign the template of static routes to one or more devices or device groups.
  5. Install the configuration to devices.