Establishing Peering Between Hub and Spoke Network
In the previous blog post, we successfully established a connection between an On-Premise environment and Microsoft Azure, creating a simple hub network topology that included a connection to the On-Premise Environment.
In this blog post, we will create the second part of the hub network topology. We will establish peering between the Hub and Spoke and enable resources to use the Azure S2S VPN Connection inside another subscription (Spoke).
Steps to Establish Peering
Open the Azure Portal and navigate to the Spoke Subscription. The name of my spoke subscription is Spoke DemoLab.
Create a new resource group.
Create a new Virtual Network.
Establish a Virtual Network peering between the Hub and Spoke Virtual Network. Navigate to the Hub VNet (in my case this is hub-vnet-1) and add peering.
Choose the following settings.
You can find the Resource ID inside virtual network properties.
Then create a peering. After creation check Peering status.
Navigate to the Spoke network and create a new subnet for virtual machines.
Create a new virtual machine and place it in the new network subnet which we created in the previous step.
Check the address space on the spoke VNet.
Connect to the RRAS Server and add a static route. We need to add the IP Address Space of the Spoke Network like we did in the previous blog post for the Hub Network.
Now you can connect to the Azure VM and the On-Prem virtual machine [NDL-CL01-MEJ]. Turn off the Firewall for testing purposes. Try to ping the virtual machines against each other
Conclusion
In this blog post, we’ve explored how to establish peering between the Hub and Spoke in a network topology.
See yaa in the next blog post! 🙂
