Validate the Azure Virtual WAN Integration CloudBlade
Validate if the Azure Virtual WAN Integration
CloudBlade is deployed as intended and the resources are created
in Azure and Prisma SD-WAN controller.
Check the status indicator on the CloudBlade window.
Once enabled and deployed correctly, the status indicator should
turn green. If the access credentials are invalid, the status indicator
will display an invalid credentials error message.
Check if the Prisma SD-WAN Datacenter site has been created
in the Prisma SD-WAN controller and if the vION HA pair has been
assigned to this site.
The Cloudblade will provision both the vION and
the set standard device name as Prisma-SD-WAN-vION-1-<region_name>
and Prisma-SD-WAN-vION-2-<region_name>. It is recommended not
to change the device name as it may lead to configuration sync issues
between both vIONs.
Go to Site Details and check if the Secure Fabric Links
are created between the newly created Azure Data Center ION devices
and the branch site devices.
Go to the Active ION device Interface configuration window
and check if Port 1 and Port 2 configurations are created.
Check if the IPs provided on port 1 and port 2 of the
element in the controller match the ION deployed in the Azure Environment.
Check if the BGP core peering between each vION and the
Azure virtual hub is up.
Verify the static route configuration for each vION interface.
Static routes are required as Azure's virtual hub router advertises
workload/application prefixes to the virtual IONs. In order for
the vIONs to forward branch traffic to these destination prefixes,
the vION(s) first need to send the traffic to the hub router and the
static route entries enable that routing.
Check the advertised application VNET prefixes to the
Virtual hub.