Azure Intersite Connectivity between Offices & Regions

Module 5 Intersite Connectivity

VNet Peering : 

VNet Peering used for connect diffrent network/office, simplest and quickest way to connect your VNets is to use VNet peering. Virtual network peering enables you to seamlessly connect two Azure virtual networks. Once peered, the virtual networks appear as one, for connectivity purposes. There are two types of VNet peering.

Regional VNet peering connects Azure virtual networks in the same region.

Global VNet peering connects Azure virtual networks in different regions. When creating a global
peering, the peered virtual networks can exist in any Azure public cloud region or China cloud regions,
but not in Government cloud regions. You can only peer virtual networks in the same region in Azure
Government cloud regions.

The benefits of using local or global virtual network peering, include:

• Private Network traffic between peered virtual networks is private. Traffic between the virtual net-works is kept on the Microsoft backbone network. No public Internet, gateways, or encryption is required in the communication between the virtual networks.
  

• Performance A low-latency, high-bandwidth connection between resources in different virtual networks.
  

• Communication The ability for resources in one virtual network to communicate with resources in a different virtual network, once the virtual networks are peered.
   
• Seamless The ability to transfer data across Azure subscriptions, deployment models, and across Azure regions. 
• No disruption No downtime to resources in either virtual network when creating the peering, or after the peering is created.
  

LAB Exercise 12- Configure VNet Peering

How to Setup a Virtual Network (VNet Peering)
As per our Lab we wanted to inter connect site A and site B.



To Implement VNet Peering follow below steps-
 
Step 1- Search for Virtual Network
Step 2- Select VNetEastUS
Step 3- Select Peerings and click Add


Step 4- Enter Name i.e - VNetEastUS_VNetEastUSB
Step 5- Select Subscription
Step 6- Select Virtual Network i.e. - VNetEastB(RGEastUS) 
Step 7- Enter Name i.e - VNetEast_VNetEastB
Step 8- Click OK

Now lets connect VM1 using download RDP file and check communication between Site A and Site B.

By Default windows firewall on and its blocking ICMP packets due to this both VM unable ping each other.   
To enable ICMP through the Windows firewall, so that you can ping this VM1 from VM2 in a later step, using  
Step 9
PowerShell:

New-NetFirewallRule –DisplayName "Allow ICMPv4-In" –Protocol ICMPv4

Step 10- Connect VM1 and VM2 and try to ping or connect using private IP 

 Site A - 192.168.0.4 &  Site B 172.16.0.4 started ping/communicate each other.

Site A - VM1
 
Site B - VM2

Step 11- Run PowerShell Command - 

New-NetFirewallRule –DisplayName "Allow ICMPv4-In" –Protocol ICMPv4

VM1 and VM3 are communicating each other. 




 

LAB 13- Configure VNet Peering  

Now Lets Setup Site C to Site A Peering.