Implement the Azure IaaS
Course-end Project 3
Description
OSS Corporation is a globally distributed firm. They have their headquarters in the East US with another
branch office in the WEST US. Currently, they are working on a project and decided that the application tier of
this project will reside in one of its branch regions. For security reasons, OSS Corporation management is
adamant on keeping their data tier in the headquarter region.
Background of the problem statement:
As an organization, they are open to suggestions and are currently evaluating Azure as a deployment
platform. To prepare for the deployment of IaaS Standard_B1ms, OSS Corporation must deploy an IaaS v2
virtual network in the headquarters region for its database. But for the application, it should create another
IaaS v2 virtual network in the branch region. In addition, because the communication between App and data
should happen over a private channel, one needs to prepare their branch office virtual network for
establishing connectivity to the headquarter’ s IaaS v2 virtual network by creating a virtual network gateway
and deploy a test IaaS Standard_B1ms VM to the virtual networks for verifying the connection.
After the deployment team ensures the connectivity between both the networks, you can validate the same
using Ping.
Following requirements should be met:
Create virtual networks in the aforementioned region
Create test virtual machines in both the virtual networks
Establish the connectivity between both the networks via VNet peering
Ensure connectivity is established properly
Step1: Create virtual networks in the aforementioned region
A) Create First Virtual Network in Headquarter (East US) Region
CIDR VNET: 10.0.0.0/16
CIDR Subnet: 10.0.0.0/24
Resource Group Name: OSS_RG_1_HQ
VNET Name: VNET-1
Subnet Name: Subnet-1
Location: East US
B) Create Second Virtual Network in Branch Office (WEST US) Region
CIDR VNET: 10.98.136.0/24
CIDR Subnet: 10.98.136.0/24
Resource Group Name: OSS_RG_2_BR
VNET Name: VNET-2
Subnet Name: Subnet-2
Location: WEST US
Step2: Create test virtual machines in both the virtual networks
A) Create First Virtual Machine in Headquarter (East US) Region
Resource Group Name: OSS_RG_1_HQ
Virtual Machine Name: VM1-HQ
VNET Name: VNET-1
Subnet Name: Subnet-1
Location: East US
B) Create Second Virtual Machine in Branch Office (WEST US) Region
Resource Group Name: OSS_RG_2_BR
Virtual Machine Name: VM2-BR
VNET Name: VNET-2
Subnet Name: Subnet-2
Location: South WEST US
Step 3: Establish the connectivity between both the networks via VNet peering
A. First got to virtual Networks Tab
B. Go to First Virtual Network i.e., VNET1
C. Go to peering tab in VNET1
Step4: Ensure connectivity is established properly
A. Connect to First Virtual Machine (VM1-HQ) East US
B. Connect to Second Virtual Machine (VM2-BR) WEST US
C. Allow ICMP traffic in Inbound Rules
D. Go to Command prompt on both the VMs by typing cmd
Then type ipconfig to check the ips of both VMs and then try to ping both VMs with each other by
the
command:
Ping <IP of other VM>
Create virtual networks in the aforementioned region
Create test virtual machines in both the virtual networks
Establish the connectivity between both the networks via VNet peering
Ensure connectivity is established properly
