Skip to content

Demonstration of configuring peering between two VNets in Azure

License

Notifications You must be signed in to change notification settings

lrakai/azure-vnet-peering

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

21 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

azure-vnet-peering

Demonstration of configuring peering between two VNets in Azure

Final Environment

Getting Started

An Azure RM template is included in infrastructure/ to create the environment:

Using Azure PowerShell, do the following to provision the resources:

.\startup.ps1

Alternatively, you can perform a one-click deploy with the following button:

Following Along

  1. Create a Linux VM with password authentication in a new VNet called dev. The VNet can be in a different region although peering data transfer costs are higher than if VNets are in the same region.

  2. Initiate a peering connection from the shared-vnet VNet with the dev VNet. Observe the status of the peering is Initiated. The peering connection cannot be used until the status is Connected.

  3. Initiate a peering connection from the dev_ VNet with the shared-vnet VNet. Observe the status of the peering is Connected. The peering connection cannot be used until the status is Connected.

  4. Use the serial console of the VM in the dev VNet to connect the the VM in the shared VNet using a private IP address:

    ssh 10.0.0.100

    This confirms the peering connection allows traffic between VNets using Azure's private backbone network (not the public internet).

Tearing Down

When finished, remove the Azure resources with:

.\teardown.ps1

About

Demonstration of configuring peering between two VNets in Azure

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published