0% found this document useful (0 votes)
209 views8 pages

Use Case:: Description

This document describes how to configure peering between two virtual networks (VNets) in different Azure regions to allow connectivity between virtual machines in each VNet. It provides steps to create resource groups, VNets with subnets, and virtual machines in each VNet. It then describes configuring the VNet peering and verifying connectivity between the virtual machines across VNets.

Uploaded by

Nagaraju Lanka
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
209 views8 pages

Use Case:: Description

This document describes how to configure peering between two virtual networks (VNets) in different Azure regions to allow connectivity between virtual machines in each VNet. It provides steps to create resource groups, VNets with subnets, and virtual machines in each VNet. It then describes configuring the VNet peering and verifying connectivity between the virtual machines across VNets.

Uploaded by

Nagaraju Lanka
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Azure VNet Peering

Use case :
Creating two Virtual Machines in different regions in two different VNet , configure peering
between to establish connection.

Description :

Create a two virtual networks as VNet 1 : 10.0.0.0/8 ; SN1 : 10.1.0.0/16; VNet 2 : 172.0.0.0/8
SN : 172.16.0.0/16, and create resource group in regions west central us, East US and create
virtual machines VM 1 , VM2 in And VNet1 and 2 are different region , configure vnet
peering

Step Wise details of Implementation of VNet Peering

Step 1 : Creating VNet1[SN1] [AkmetRG1] and VNet2 [SN2][AkmetRG2]


Step 2 : Creating VM1 [AkmetRG1] and VM2[AkmetRG2] – win server 2016
Step 3 : Check Connectivity between VM1 and VM2 before VNet Peering using RDP/mstsc
Step 4 : Configure VNet Peering between [Vnet peerings] Vnet1-to-Vnet2 & Vnet2-to-Vnet1
Step 5 : Verify VNet Peering Connectivity post configuration

@Akmet
Creating Resource Groups
Step 1 : Create a resource group
1. Login to azure portal
2. Create a resource : AkmetRG1& AkmetRG2
3. Navigate to Resource blade and check resource
groups are created in regions East US & Central US
respectively

@Akmet
Create VNet, Subnets
Step 1 : Create a Virtual Networks VNet1[SN1]
[AkmetRG1] & VNet2 [SN2][AkmetRG2]

1. Login to azure portal


2. Create a VNet1 [10.0.0.0/8 ; SN1 : 10.1.0.0/16],
VNet2 [172.0.0.0/8 SN : 172.16.0.0/16]
3. Navigate to virtual network blade and check
vnets are created along with subnets.

@Akmet
Create Virtual Machine
Step 1 : Create a Virtual Networks VNet1[SN1] [AkmetRG1] & VNet2 [SN2][AkmetRG2]

1. Login to azure portal, Navigate Virtual Machine blade and create AkmetVM1 & AkmetVM2

@Akmet
Configure Networking details

Click on Review and Create


VM validation and Creation
Verify VNet Peering Connectivity
Step 1 : Login to Virtual Machines and check
1. Take the Private IP of VM1 and try to login from VM2 using mstsc / RDP
2. Connection fail
3. Navigate to Resource blade and check resource groups are created in regions East US & Central
US respectively

@Akmet
Configure VNet Peering
Step 1 : VNet Peering Configuration
1. Navigate Virtual Network blade and click
on peering , provide peering link name for
both and click on add
2. Connection successful
3. Now try to login to VM1 from VM2 using
mstsc / RDP , successful

@Akmet

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy