Validate the Azure Virtual WAN Integration CloudBlade
Table of Contents
Expand All
|
Collapse All
Prisma SD-WAN Docs
-
-
-
-
- AWS Transit Gateway
- Azure vWAN
- Azure vWAN with vION
- ChatBot for MS Teams
- ChatBot for Slack
- CloudBlades Integration with Prisma Access
- GCP NCC
- Service Now
- Zoom QSS
- Zscaler Internet Access
-
-
- ION 5.2
- ION 5.3
- ION 5.4
- ION 5.5
- ION 5.6
- ION 6.0
- ION 6.1
- ION 6.2
- ION 6.3
- ION 6.4
- New Features Guide
- On-Premises Controller
- Prisma Access CloudBlade Cloud Managed
- Prisma Access CloudBlade Panorama Managed
- Prisma SD-WAN CloudBlades
Validate the Azure Virtual WAN Integration CloudBlade
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.Go to WorkflowsPrisma SD-WAN SetupData Centers to check if the controller has created the Prisma SD-WAN Data Center site and assigned the vION HA pair to this site.The CloudBlade will provision both vIONs and set the standard device names as Prisma-SD-WAN-vION-1-<region_name> and Prisma-SD-WAN-vION-2-<region_name>. It is recommended not to change these device names, as doing so may cause configuration sync issues between the vIONs.Select the site name to 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.Check the received routes from the Cloud Router.