Overcoming Asymmetrical Routing in Azure Virtual WAN

Overcoming asymmetric routing in Azure Virtual WAN: A collaborative journey

In the rapidly evolving cloud networking environment, professionals often face complex challenges that require innovative solutions. This blog post details a recent scenario involving Azure Virtual WAN (VWAN) where teams began collaborating to solve an asymmetric routing problem. This case study not only highlights the technical complexity, but also the importance of collaboration and knowledge sharing in the technology community.

assignment:

The key issue was related to asymmetric routing within the Azure VWAN architecture, which included two hubs located in different regions. The primary goal was to ensure seamless connectivity between the Palo Alto NGFW on one hub and Panorama on the other hub without disrupting the existing VPN default path. Asymmetry in routing was particularly problematic for traffic trying to reach Panorama from NGFW. This is because return traffic defaults to going through the VPN, diverting it from the intended path.

Possible solutions:

1. Expose Panorama to a public IP and create a relay subnet for the NCUS to SCUS routing/advertising summary path for the NCUS subnet (10.193.0.0/16).