Azure

Overview Of Azure Site visitors Supervisor And Configuring Precedence Primarily based Endpoints

Introduction – Azure Site visitors Supervisor

A DNS-based site visitors load balancer is Azure Site visitors Supervisor. This service enables you to disperse site visitors to your public-facing purposes amongst Azure areas internationally. For particular instances, Azure affords a set of absolutely managed load-balancing choices.

Azure Site visitors Supervisor Routing Strategies

Precedence

Once you select precedence routing, a prioritized record of service endpoints seems, with the first service endpoint receiving the best precedence for all site visitors. If the first service endpoint is down, site visitors is routed to the subsequent highest precedence endpoint, and so forth.

Weighted

Once you wish to distribute site visitors uniformly or make the most of pre-defined weights throughout a group of endpoints, you employ the weighted routing method. On this traffic-routing method, you assign a weight to every endpoint within the Microsoft Azure Site visitors Supervisor profile configuration, which is an integer starting from 1 to 1000.

Efficiency

Once you want to enhance the responsiveness of a number of apps by routing site visitors to the place nearest to the consumer, this site visitors routing technique is utilized. The ‘closest’ endpoint is not all the time the one with the shortest geographic distance. As a substitute, the ‘Efficiency’ traffic-routing mechanism makes use of community latency to pick the closest endpoint.

Geographic

Every endpoint linked with a profile should have a set of geographic areas allotted to it in geographic routing. When a area or a gaggle of areas is assigned to an endpoint, all requests from that area or set of areas are routed solely to that endpoint.

Multivalue

For Azure Site visitors Supervisor profiles with solely IPv4/IPv6 addresses as endpoints, you possibly can select MultiValue. All wholesome endpoints are returned when a query for this profile is acquired.

Subnet

To map units of end-user IP deal with ranges to a particular endpoint inside an Azure Site visitors Supervisor profile, make the most of the Subnet traffic-routing mechanism. When a request is acquired, the endpoint that’s returned is the one that’s mapped to the supply IP deal with of the request.

On this situation, I will current two digital machines which were related into Azure Site visitors Supervisor and are prioritized.

I’ve already created a Useful resource Group Named Az_TM_RG

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step

Now I’m going to create a Digital Community

Step 1

Search Digital Networks and Create Digital Community

Protecting Default for IP Deal with House and Subnet

Overview + Create

Step 2

Now I’m going to create two Digital Machines and putting in IIS Position

Digital Machine 1

Choose the Digital Community and Preserve the Subnet Default

Overview + Create

Create the Second VM additionally as above Configuration

Step 3

Now I’m going to Automate the IIS Set up on Each Azure Digital Machines

Run beneath Question in Cloud Shell

Change the Highlighted Useful resource Group title, VM title, and Location as your Configuration.

Set-AzVMExtension -ResourceGroupName “Az_TM_RG” -ExtensionName “IIS” -VMName “TM-VM1” -Location “EastUS” -Writer Microsoft.Compute -ExtensionType CustomScriptExtension -TypeHandlerVersion 1.8 -SettingString ‘{“commandToExecute”:”powershell Add-WindowsFeature Net-Server; powershell Add-Content material -Path “C:inetpubwwwrootDefault.htm” -Worth $($env:computername)”}’

This may take 5 to 7 minutes and alter the highlighted values to Second Digital Machine and Run once more the modified script to put in IIS Position in second VM.

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step

Copy the Digital Machine public IP and browse in your browser then you possibly can see the VM Identify as beneath, (Examine together with your second VM additionally)

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step

Step 4

Earlier than creating the Azure Site visitors Supervisor profile, we have to configure DNS Identify for each Digital Machines,

Navigate to Digital Machines, DNS title Click on Not Configured.

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step

Choose the DNS title

Save.

Repeat the above situation for second Digital Machine additionally.

Step 5

Now we’ll create an Azure Site visitors Handle Profile,

Search Site visitors Supervisor

Create Site visitors Supervisor Profile

As I described above routing strategies, now you possibly can choose the required routing methodology as your requirement and on this situation, I’m going to make use of Precedence Primarily based routing Technique.

Create.

It would take as much as 5min and examine by Refresh.

Click on the Created Site visitors Supervisor Profile and Navigate to Configuration and you’ll see the Endpoint Monitoring Choices.

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step

Now Navigate to Settings Tab – Endpoints and Create

Now you possibly can see the Endpoint Sorts as beneath,

Azure Endpoint

Use this sort to load-balance site visitors to a cloud service, webapp or public IP Deal with in the identical subscription.

Exterior Endpoint

Use this sort to load-balancer site visitors to any fully-qualified area title (FQDN), even for purposes not hosted in Azure like you need to use OnPrem

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step.

On this situation, I’m deciding on Azure Endpoint since I’m going to make use of created two Azure digital Machines and as Goal Useful resource, I’m deciding on Public IP Deal with

Click on Add.

Click on Add once more to Add second Digital Machines as Endpoint and Repeat the above situation and choose the precedence as precedence 2.

I’ve chosen Precedence 1 because the TM-VM1 and as Precedence 2 TM-VM2.

After jiffy Monitor Standing will change Checking Endpoint to On-line.

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step

Now navigate to the Overview web page and duplicate the DNS Identify and paste within the browser, then you’ll get the Precedence 1 Digital Machine Identify.

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step

Step 6

Now Flip off the TM-VM1 Digital Machines and can see the Site visitors is navigated to Precedence 2 Digital Machine.

Go to Digital Machines – Choose Digital Machines 1 (TM-VM1) and Click on Cease. (Should you want you possibly can reserve the general public IP Deal with for that Digital Machine)

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step

Now Navigate to Site visitors Supervisor Profiles,

Click on the Profiles and Navigate to Overview Web page and Refresh the Web page,

It is possible for you to to see the Digital Machines 1 Endpoint (ArticleEP) Monitor standing is Degraded because it’s not on-line.

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step

Now copy the DNS Identify and Browse and you’ll get the second Digital Machine title (TM-VM2)

Overview of Azure Traffic Manager & Configuring Priority Based Endpoints Step by Step

Abstract

We realized the Overview of Azure Site visitors Supervisor and all routing Strategies and realized how one can deploy and Configuring Precedence Primarily based Endpoints Step by Step. Please go away a remark within the remark field when you have any questions.

Show More

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button