Welcome to my first write-up on Azure Traffic Manager using Geographic Routing. Let’s begin with a basic introduction to Azure Traffic Manager before getting into detail with it.
Azure Traffic Manager
Traffic Manager is used to route the traffic between your application which runs on the server machine subjected to be Windows or Linux. Here, in Traffic Manager, we have four different types of routing methods-
- Priority Based Routing
- Performance Based Routing
- Geographic Based Routing
- Weighted Based Routing
Priority Based Routing
In Priority Based Routing, we set priorities for the servers connected with the help of Traffic Manager. The request gets routed with the help of the priorities that have been configured.
Performance Based Routing
In Performance Based Routing, you will be able to access the applications on the server machine based on the lesser time of retrieval.
Weight Based Routing
Geographic Based Routing
In Geographic Based Routing, depending on your Geographical location of access, your Traffic Manager will route the incoming connection towards the nearest geographical location of your application.
In the below demo, we will be working with Geographic based Routing in Traffic Manager. We will be creating two server machines one at South India location and the next one at Central India by which we are going to access the application based on the nearest point of access. Our end-users who will be pinging from India will be routed to South India’s DC and other requests from Hong Kong will be routed towards Central India’s DC. To create a scenario of accessing data from Hong Kong location we will be using VPN with help of Zenmate.
Let’s get on with the demo!
Requirements
- You should have an Azure account, if not click here to get an Azure account which will be a free trial one for a month.
- VPN (Virtual Private Network) – any free VPN like Zenmate.
Get added with the Zenmate extension from your browser. For reference, look below.
Follow the below step by step procedure.
Step 1
Login to the Azure account of yours by clicking here.
Click on New - Compute - Windows Server 2012 R2 Datacentre.
- New
- Compute
- Windows Server 2012 R2 Datacenter.
Step 2
You will be getting four blades as Basics, Size, Settings, and Purchase which you have to configure for creating a new Virtual Machine.
For Basics,
- Name: Enter your Virtual Machine name.
- VM disk type: Select your Virtual Machine Disk Type either as HDD or SDD.
- Username: Mention the login username for your server.
- Password: Password for your server.
- Confirm Password: Confirm the same as previous.
- Subscription: Select the active subscription of the one which you own.
- Resource Group: Either create a new resource group or select the existing one which you have.
- Location: Your preferred Datacenter Location, here we have selected South India.
Click on OK to move to the next blade.
Step 3
Select the size for your Virtual Machine; I have selected A1 based on my usage. Click on "Select" to move on to the next blade of Settings.
Step 4
Configure your NSG (Network Security Group) settings by adding an inbound rule which sets a priority, source, source tag, service, protocol, port range and action. Click on OK followed by it.
- Name – Internetrule
- Priority – 200
- Source – Tag
- Source Tag – Internet
- Service – Custom
- Protocol – TCP
- Port range – 80
- Action – Allow
Click on "Purchase" after validation on the final blade of summary.
Note
Repeat the above steps of 1-4 to create another instance on the DC location of Central India.
Step 5
Join the conversation! Your thoughts help the community grow.