So we just finished talking about two of my rationales, two of our reasons for adjusting on network optimization. We talked about our late and see sensitive applications, and we talked about our high bandwidth usage applications. Now we're gonna talk about up time. So what is up time? Well,
for people that are network administrators of people, rather, systems administrators are people that are trying to run an I T. Infrastructure. In general, up time is very, very important. Up time is the percentage of time that are service's are available.
That the person it's essentially how much time out of the year, how much time out of the month, the week, the day
our applications are up and running and available to service clients.
our I team environment doesn't just live in a bubble. Our I T infrastructure is isn't just there for the sake of being an I T infrastructure. It's there to service the company. It's there to service a government. It's there, too.
It's there as a function to service in users so that they can also get work done.
So we need to make sure. But we have a very strong up time because we want to make sure that whatever the reason, that I t infrastructures. Therefore, whatever the reason our network is here for people are able to use it to get work done. And the less and the
the first hour up time is, the less people are, the less time people are actually able to utilize our network and get get things done, the worst that reflects on us. Because when they're not able to get work done, they want to know Ryan. And then when they say Well, it's because the network is down
They take a look at us and they say
All right, what's up?
So we need to make sure that we have a strong a very strong up time. A percentage of time are service's are available now the needs for this very depending on what type of service is we're providing and what our business model is
if we're, say, a small If, uh, we're supporting aid
network backbone for maybe a small a small gym of small 24 hour Jim Well, their network and their Internet connectivity may not be as critical if they're able to, if they're not able to connect out, then say a site that they provide completely online Health Service's
If their network connectivity to their service is down, then they're not making sales was if we're servicing the network connectivity for a gym. Well, their Internet connectivity may not be as critical because people customers are still able to come in and they're still able to work out at the gym, and they're still able to apply for memberships, things like that.
But we need to understand how our needs very depending on our different service is depending on our exact company that we're in. And we need to understand what emphasis and how much money we can pour into maintaining a better up time on our network.
Now, many times, this comes in the form of an S L. A S s stands for our standard lease agreement. And what this means is this is theater agreement that we're making with the company that we're providing I T service is for. And we're saying
that we are going to guarantee this percentage up time we're going to guarantee
this quality I t service is for your network and with the hot the better up time we have, the better the better network backbone and the more that we can promise them, the more costs associated with that. If we have a giant data center that we can promise is going to be, is going to have an up time
is only going very strong up. Time is only going to be down
five minutes out of the year. Then there's going to be a higher cost associated with that. Then if we went to that same data center and said
Okay where we can weaken do up to one week
out outage time throughout the year so that one week outage time is gonna come with a little cost than the five minutes outage time and depending on their needs,
they may go with the one week or they may go with the five minutes, depending on their budget, on depending on their needs, et cetera.
But that's a that's a lot higher level project Project management type concerns our network. Our network plus level concerns are going to be with this part are going to be the different components of making sure that we have a good up time
and this is going to be things such as redundancy in our network. We may have additional routers or additional switches that stand his backups. We may have secondary network interface cards in different servers.
We may have different power backups if the power goes out to the building. We made me to make sure that our different network devices have some sort of battery backup so that they're still able to perform network functions. We may even have a Senate, a secondary Internet connection. Maybe we have a primary Internet service provider that they that
we promised our company.
Okay, we're gonna have a down time of only two hours a year.
But our Internet service provider can only promise a up time up to
300 up to one year minus two weeks, they say. Yes, throughout the year, there may be an accumulated downtime of two weeks. Well, that's not gonna work with us, promising the company that they're only gonna have a down time of two hours per year because the Internet may go out and then
that's not in our hands. We have to go to the Internet service provider. We need to have them fix it
and they say, Well, we already told you You may be down up to two weeks per year so we may hire We may go out and we may find us another Internet service provider that provides a secondary Internet connection in that maybe a little bit slower but still provides connective ity. So if our primary Internet service provider fails
that, we soak, amuse that secondary Internet service riders connection
while that primary Internet service provider comes back up. So these are different things we need to take into consideration these air different every component from point A to point B needs to be taken into consideration when we're considering our up time. We want to do things like minimizing our single point singular points of failure.
network bottleneck that all the network data and all the network traffic is redundant and has backups all the way to this router and the Miss Router is
where all of our data goes through, then if that rather fails, then we're down and we have to replace that router. We need to make sure that we have some sort we want to eliminate. We want to eliminate single point of failure as much as possible. It may not be feasible to eliminate all of them, but not to eliminate as many as possible.
We don't want to be running.
We may not want to run network backbones that are our only network backbone. That service. Our service is our entire environment in one bundle that runs through the ceiling above someone's office. If there maybe there's a fire in that office or maybe some sort of corporate corporate
corporate sabotage, someone comes in and finds out where that is. And they just take Cem
gardening shears and they just cut it. One man, We have a pretty big problem, so we need to make sure that we have some sort of redundancy. We want to reduce those single points of failures as much as possible. So now that we know that up, time is and we know sort of a general overview of
up time being how much percent how much percentage of the time
our network is available to users? Let's take a look at some. Let's take a more in depth look at some of the methods that we can use in order to make sure that we have that in our network