Hello and thanks for joining me for Cyber Aires. Microsoft Azure Administrator A Z 103 Course. This is Episode 45 as your traffic manager, and I'm well, Carlson.
In today's episode, we're gonna discuss the benefits of traffic manager and what it is. We're also gonna talk about the way that it does the job that it does for us using certain routing options.
We'll talk a bit about the difference or how traffic Manager is different from load balancer. And we're gonna do all this while we're configuring the traffic manager in Portal as well
to jump right into traffic Manager. Let's get into portal here and, as we've done many times, will come to the top
and search for traffic manager. We're gonna click on traffic manager profiles, go ahead and get started.
We're gonna create a new traffic manager profile here
and you'll notice that
this name is part of a girl and oftentimes an azure. When we see that, that's a clue to us that this is going to have to be globally unique so we cannot use
the name that's already been used
or it will fail. However, as soon as we make this a unique
We get the green light.
Now, this is where traffic manager goes ahead and gets interesting now. So what generally is traffic manager? Well, traffic Manager is a way to rout Internet traffic using D. N s to an end point of our choice. So it's similar in some ways to a load balancer.
But the main differences here of Traffic Manager are that
primarily it uses d. N s to do the job that it does. We'll need an http or in https in point to set up monitoring.
We can send traffic to Azure V EMS as your cloud service is as your Web APS. And we can even send traffic using traffic monitor
traffic manager to a completely external in point. And that could be 1/3 party Web site on another provider or an on Prem piece of equipment that hosts an application is Well, the last difference here between traffic manager is that it is only going to support Internet traffic. You cannot use traffic manager for internal traffic
because traffic manager uses D. N s.
We're going to have to be accessing the traffic manager with D N s in tow. Internal D N s will not work again. Traffic manager is for public traffic on Lee.
Now, how does Traffic Manager do the magic that it does? That's gonna be based on this routing method here, and you can see that we have a number of options.
So the performance option here at the top is going to use Leighton. See? And it's gonna use the lowest Leighton see option that we have available to us. So this is gonna be really great if you want the best performance possible.
So the example here would be that you have workloads. Let's say, Web maps, for example, deployed to a number of different data centers in the azure environment across the globe.
A user is going to use our traffic manager I p address to try to access that Web app, and they're going to be sent to the one that has the lowest lightens the possible.
You're probably thinking that this sounds a little bit like a seating in, and it does share some similarities, but it's not exactly the same.
It is going to require a little bit more work on our part to manage the resource is that traffic manager is ultimately standing traffic to Where's the CD and in points are completely hands off on our part. And it really is a service that we're deploying
Awaited routing method here is going to be where we can send an X percentage of our traffic toe, one endpoint and another percentage traffic toe. Another end point
priority's gonna be similar, but we can set the priority from 1 to 3, whatever the priority of the endpoint is going to be. And this is particularly useful for setting up things like fail over patterns so you could have your main in point be set to the highest priority,
and then you could walk down a backup chain with diminishing priorities as you go.
A geographic routing method is gonna be exactly what it sounds like. But the way this works is that traffic manager is going to be looking at the I p address of where the D. N s is coming from. So the D. N s source i p. And whatever that I p address geography resolves to traffic manager is going to send your users
tow whatever geography region address has its closest to that end user
and those are gonna be the primary routing methods that are gonna be relevant here for a Z 103 So for the sake of argument, we're gonna go ahead and leave this on performance, our subscription and free trial. We're gonna pull down this resource group here.
We're leaving this in Central US region and we're gonna create this traffic manager.
Let's go ahead and look at this traffic manager that we've already deployed. We can see some of the options here that we have
here in the overview blade, we can see the D. N s name. That's ultimately gonna be how we navigate to and take advantage of traffic manager to get to whatever resource is we haven't connecting to.
We can also come here into the configuration settings and change some of the settings here of the traffic manager, such as the routing method that we just previously selected.
We also have some options here on how the traffic manager is going to be monitoring the end points that we're going to add in just a minute.
We have three options. Http https and T c p. We're gonna go ahead and leave this at http. Import 80 and there's a path that we can watch as well. So if there was a particular web page that you wanted this to be monitoring, you could go ahead and put that here in the path
we can see done here that it's gonna be probing every 30 seconds. And we can change that here to a 10 seconds. Should we choose to,
We're gonna be tolerating three failures. So is on with its less than three. We don't have any problems here,
and it's gonna be a failure if the probe doesn't get responded to within 10 seconds. And I can change that. Here is well,
really user measurements is gonna be a pretty interesting feature that's similar to, say, tracking on a website. So you're gonna embed code in your Web property here is azure refers to it,
and any time that property loads, it's going to be sending back information on late and see to the azure traffic manager.
You can come down here and enabled traffic view so that you can see some information about how traffic managers working where your traffics coming from. It's really pretty interesting should you wanna know more about enabling traffic view? Definitely click on the pricing info before you do so.
And the important part here in Traffic Manager is assigning an end point to this particular traffic manager profile. We're gonna come in here to end point and we're going to select add
we're gonna name our in point and then we can select the target resource type called Service APP Service AB service lot or public I P address. And we could use his public i p address to route traffic to an external resource outside of Azure.
You could select the I. P. Address that you ultimately wanted to include us an end point, and then you could hit okay to apply those changes. Now, you'll notice here that we Although we have some public i p addresses here in Azure,
these are gonna be great out. And if we look at the information on the tool to that's gonna be because no. D. N s name or publicly and s, it's currently configured on this particular resource. So he wanted to take advantage of traffic manager. We're gonna need to have d. N s up and running again traffic manager does its job by using d N s to get the work done.
We're gonna come back out here to this traffic manager
because I want to mention here real quickly. What are the benefits of traffic manager? Why would we want to use this over a load balancer?
Now, traffic manages pretty interesting because it does do the endpoint health checks, which we looked at here when we went to the configuration blade. So every 30 seconds, it's gonna be probing to do health checks on all of our end points and it's gonna auto fail over. So if one of those in points fails, traffic managers not gonna send traffic to that end point any longer,
this ultimately is gonna increase the up time of all of our end points.
Imagine if you have a number of Web APS deployed all across the United States and various different regions. You could even have multiple V EMS in the same region for multiple Web gaps in the same region in traffic manager. And as long as those Web maps were online, traffic manager would continue to route traffic to them. But if any of them went down
traffic manager is going to stop routing traffic to those Web, perhaps that have failed.
You can also use things like Leighton See and geography routing to make sure that you're sending users to the closest endpoint to them and yet still have control over those in points, which is something you lose when you deploy via CD in
Traffic. Manager also allows you to updates during normal business hours because it is monitoring for up time and it auto fails over.
Another interesting thing about traffic manager is that you can use an on premise or a cloud workload both within Azure or another cloud provider. As long as it's public traffic. Using D. N s traffic manager can round it wherever you would like for it to go.
You could even go through the process when you're creating your traffic manager profiles and nest them in relatively complicated ways to get some really interesting things done as faras routing and traffic manager aren't concerned.
So in today's episode we talked about what traffic manager does, which is basically taking public Internet traffic, leveraging the use of D. N s and giving us control over where we would like for that traffic to end up through a number of different routing methods.
We talked about what those routing methods are so priority performance, geographic and waited being relevant here today.
And we step through the process of how we actually configure traffic manager here in the azure portal.
Coming up next, we're going to step through a really interesting tool called network Watcher that allows us to have some visibility into theat as your environment and into its network.
Cloud providers are not known for giving a lot of visibility into their networks for some obvious security reasons, which can often times make networking troubleshooting relatively difficult when it's traversing the provider's network.
But Azure has a really interesting tool in network watcher to help us troubleshoot problems within networking. Thank you so much for joining me today, and I'm looking forward to our last networking video coming up very soon.