Planning the network

Following are the settings chosen for this deployment, such as IP address networks, BGP autonomous system number (ASN), performance SLA criteria, and so on:

Option	Description
Overlay network address space	This address space is used for the IP addressing of all hub and branch devices. The default 10.50.0.0/16 is used.
Loopback IP address space	These addresses are used for performance SLAs, router IDs, and other admin operations. The default 172.16.0.0/16 is used.
BGP ASN	A private number is used and must remain exclusively for this SD-WAN BGP configuration. You must use the same ASN used in Deploying FortiGate NVAs in vWAN hub. In this example, the ASN is 64512.

The deployment example in this guide uses the fullowing ports and IP addresses:

Azure vWAN hub consists of two FortiGate NVAs.
vWAN FortiGate NVAs have ‘port1’ configured for external access.
- IP and routing are retrieved through Azure DHCP.
vWAN FortiGate NVAs will advertise port2 to directly connected network and all routes received from Azure vWAN services.
- Azure private VNET is advertised through Azure vWAN BGP services.
Branch devices are connected to ISP1 on port1.

Planning the network

Following are the settings chosen for this deployment, such as IP address networks, BGP autonomous system number (ASN), performance SLA criteria, and so on:

Option	Description
Overlay network address space	This address space is used for the IP addressing of all hub and branch devices. The default 10.50.0.0/16 is used.
Loopback IP address space	These addresses are used for performance SLAs, router IDs, and other admin operations. The default 172.16.0.0/16 is used.
BGP ASN	A private number is used and must remain exclusively for this SD-WAN BGP configuration. You must use the same ASN used in Deploying FortiGate NVAs in vWAN hub. In this example, the ASN is 64512.

The deployment example in this guide uses the fullowing ports and IP addresses:

Azure vWAN hub consists of two FortiGate NVAs.
vWAN FortiGate NVAs have ‘port1’ configured for external access.
- IP and routing are retrieved through Azure DHCP.
vWAN FortiGate NVAs will advertise port2 to directly connected network and all routes received from Azure vWAN services.
- Azure private VNET is advertised through Azure vWAN BGP services.
Branch devices are connected to ISP1 on port1.

Secure Networking

Hybrid Mesh Firewall

NOC Management

LAN

WAN

Unified SASE

Single Vendor SASE

Cloud Network Security

Secure Endpoint Connectivity

Web Application / API Protection

Security Operations

Security Operations Automation

Identity

Early Detection & Prevention

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 Pillars

Cloud

Popular Solutions

Azure vWAN SD-WAN NGFW Deployment Guide

Planning the network

Planning the network

Planning the network