Assign tags to objects in the Prisma SD-WAN Portal
Lets see how to assign tags to objects in the Prisma
SD-WAN portal.
Once the CloudBlade is configured, the next
task is to tag Prisma SD-WAN sites and interfaces to denote which
sites and interfaces are candidates for integration with Azure Virtual
WAN.
From the Prisma SD-WAN portal, select the site
that needs to be tagged and click the edit icon.
In the TAGS field, add the
azure_enabled
tag. The
tag is case sensitive.
Click
Done
.
The site has been tagged and enabled for Azure vWAN. Now,
tag the interface that can be used to establish a Standard tunnel
to vWAN.
From the site summary screen, click the device name to
enter the device configuration screen. Locate the interfaces tab,
select the interface connected to the circuit you want to use to
build the tunnel to Azure, and add a region-specific tag that
corresponds to the region the vWAN Hub you want to connect to is
in (e.g.
azure_enabled_eastus
).
This
interface must have a public IP address configured statically or
via DHCP, or if behind a NAT device one must have the
External
NAT Address & Port
defined under the Advanced Options
for this interface.
Due to an Azure vWAN limitation, with
version 1.0.1, only one interface can be tagged and used to build
the tunnel to a single vWAN hub in Azure.This limitation does not
allow the use of multiple transports to reach the same vWAN hub.
From 2.0.1,with the limitation removed from Azure, multiple interfaces
can build tunnels to the same vWAN Hub, allowing the use of these
tunnels in active/active mode to reach the vWAN hub.
Once this configuration is complete, during the next
integration cycle (approximately 60 seconds), Standard IPSEC tunnels
to connect the Prisma SD-WAN ION and Azure vWAN Hub begin the creation/onboarding
process. It may take several integration cycles for the tunnels
to appear and be active on the Prisma SD-WAN portal and the VPN
site objects to show up in the Azure portal.