Fortinet black logo

Examples

Naming conventions

Naming conventions

The examples in this guide often use the following variables:

Variable

Description

Value

ul-id Underlay ID

1 for INET

2 for MPLS

branch-id Branch ID

1 for Branch1

2 for Branch2

dc-id Datacenter ID

1 for DC1

2 for DC2

overlay-id

Overlay ID

<ul-id><dc-id>

The overlay-id variable deserves a bit of an explanation. Because Spokes will build tunnels to each of the Hubs over each of the underlays, effectively we will have 4 separate overlay networks. And we will identify them by the combination of the other two variables (<ul-id><dc-id>):

Underlay

Hub

Overlay ID

INET

DC1_FGT

11

INET

DC2_FGT

12

MPLS

DC1_FGT

21

MPLS

DC2_FGT

22

As you will see, all these variables will be often used in naming and IP addressing, which will be particularly crucial when we define CLI templates.

To begin with, LAN subnets on each site are defined as follows:

Site Type

LAN Subnet

Branch

10.0.<branch-id>.0/24

DC

10.<dc-id>.0.0/24

Naming conventions

The examples in this guide often use the following variables:

Variable

Description

Value

ul-id Underlay ID

1 for INET

2 for MPLS

branch-id Branch ID

1 for Branch1

2 for Branch2

dc-id Datacenter ID

1 for DC1

2 for DC2

overlay-id

Overlay ID

<ul-id><dc-id>

The overlay-id variable deserves a bit of an explanation. Because Spokes will build tunnels to each of the Hubs over each of the underlays, effectively we will have 4 separate overlay networks. And we will identify them by the combination of the other two variables (<ul-id><dc-id>):

Underlay

Hub

Overlay ID

INET

DC1_FGT

11

INET

DC2_FGT

12

MPLS

DC1_FGT

21

MPLS

DC2_FGT

22

As you will see, all these variables will be often used in naming and IP addressing, which will be particularly crucial when we define CLI templates.

To begin with, LAN subnets on each site are defined as follows:

Site Type

LAN Subnet

Branch

10.0.<branch-id>.0/24

DC

10.<dc-id>.0.0/24