none
Looking for detailed steps on configuring a express route from on premise to the cloud? RRS feed

  • Question

  • Looking for detailed steps on configuring an express route from on premise to the cloud as well as providing a way for vnets to communicate with other vnets/on premise?

    Are there any prerequisite configurations that need to be done on premise?   Do we need any special gateways configured in the Vnets?   We will be using several vnets to include: 1) vnet 2- management apps- requires jump servers, 2) vnet 1 - path for traffic from on premise to other vnets, 3) vnet 3- production, 4) vnet 4 - development, 4) vnet 5 - test.   All traffic with the exception of management traffic will all pass through vnet 2.    Is there a type of virtual router (ie AWS has a virtual gateway which is a SaaS which acts like a router) so that traffic can communicate between vnets in the cloud while allowing for communication with on premise {vnet 1 (all cloud bound traffic except management traffic) and vnet 2 (management traffic like jump servers) would both need to communicate with on premise}?  

    It seems like there is no such azure offering for a virtual network interface that allow communication between vnets?  I only noticed a hub vnet which communicates with the on premise via a express route gateway.   This hub and  spoke seems to only allow communication with the hub?  Wanting to reduce or simplify the cloud peering configurations. (see diagram in the link)  We were expecting to have vnet have peering connections to this virtual gateway (which would have to act like virtual router service) allowing for communication between the vnets in the cloud.   Vnet 1 ( all traffic expect management) and Vnet 2 ( management) would be the entry point for traffic in the cloud.

    https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/hybrid-networking/hub-spoke

    XXXXXXXXXXXXXXXXXXXXXXXXXXX

    https://github.com/microsoft/Common-Design-Principles-for-a-Hub-and-Spoke-VNET-Archiecture


    noted under Hub and Spoke Architecturer in the above link (2nd bullet - Spoke Vnets) that they are not transitive.  Please confirm my understanding because we need the spoke vnet to communicate with each other.  Therefore would our requirement for transitive communication between  spoke vnets using peering? ( this requires a lot of peering ) or do we need a  virtual router allow communication between each spoke vnet?  Communication with this router would not require a peering?



    • Edited by kimdav111 Thursday, November 7, 2019 2:55 PM
    • Moved by FemisuluModerator Friday, November 8, 2019 12:14 AM better suite here
    Thursday, November 7, 2019 1:45 PM

All replies