Transcripts
1. Instructor & Course Introduction: Hi and welcome to this class. My name is Amelia. I'm an IT professional and Trina and have been working in IT for over 20 years and I absolutely love it. And over the next number of videos, we're going to be giving you the skills that you need to be a better IT professional. We're going to be covering a lot of material around the basics for every IT tech, every administrator, every engineer. These are the things that I have learned throughout my Korea and these are the things that I would recommend for you to be better and get better in your IT skillset. So whether you even starting out in IT, whether you've been in technology for a little while, we're going to be covering the foundation or the essential to a little bit more of the advanced. Now this is a plethora of knowledge. We're gonna be giving you a no, a lot of knowledge. What I would recommend is get yourself a laptop as you are following along and take notes. Every one of my videos because you're watching this online, The great thing is that you can go back and re-watch every single video again, every single class again, which is excellent. But we're going to be covering a lot of material. Now. Something that I would also recommend is if he can demo this yourself, please try to demo this yourself. We are going to be talking about service. So what did she go and build yourself some virtual service and play around with some of the technologies that we're talking about. We're gonna be talking about networking. So why don't you look and get yourself a network lab. We can understand a little bit more about what a raspberries firewall is. We're going to be talking about back-ups. Would have back-ups do have backups get configured. So why don't you go and try to build your own backup environment and backup some paces and some servers that you may have in your lab. For me, the best way that I learn is by re-watching, by repetition, going through it again. But even better is doing it yourself. So definitely recommend have yourself one or more spake computers available to you. You can actually go and play around with this stuff yourself. You can actually build, test, and learn as you're going through this course. And my recommendation to you is make this a project for yourself at the end of every class, let me know how you've gone. Once you've learned something, let me know what you learned out of that, let me know if you've got any questions. What did she comment and let me know. And there are others who will be watching this course that may also be able to help you and contribute to your learning throughout this class. So there's an introduction to a detailed list of classes that will be coming up. Thanks again for checking this out. Hopefully, you learned a lot.
2. IT Support Levels (Lvl 1, 2, 3): So even be in defining these three levels, just be aware that they can vary depending on the company, depending on the size of the company, whether if it's a small, medium, or large business, depends on the type of company it is as well. Because some companies may have level one, level two, level three. Other companies may not have such a definitive change between a level 1, 2, and 3. That could be blade, you know, sort of crossover between all of these roles. Some companies, if they're smaller, my only have one or two IT people taking on multiple responsibilities between a level 1, level 2, and level 3. As long as you're aware of that, it can change from company to company. Definitions can change from company to company. But my experience having worked in IT for a very, very long time, having worked in a lot of different companies, I have seen many combinations. So hopefully I can give you some ideas and give you my best definitions for the differences between a level 1, level 2, and level 3. So level one is somebody who has perhaps only just entered the IT field. Perhaps I've just graduated. They just got themselves the university or college degree, whatever it may be. Maybe a couple of search under their belt and they just starting off in IT. That may not always be the case because I've made a lot of level 1 people that really like that level one role. And they likely to stick with that even though they've been in the industry for a long time. But generally a level one will be a help desk person or a service desk person. So you can sort of have those two roles interchangeable. Somebody who looks after the help desk, somebody who is managing the help desk or managing the service desk, they don't have to be super, super skilled in IT. They should know the basics of IT to be able to provide basic levels of IT support. They're going to be perhaps on the phone, picking up phone calls from the end-users, from a users in a company or used in another company. So for example, if they're working in a managed services provider performing IT support for other companies, they could be the very first of contact for an end-user, for a customer. They calling up, they have an issue with a computer, right? The level one person will try to troubleshoot and try to fix that issue if they can. They could also be doing things such as resetting passwords, providing basic access to staff, understanding what Active Directory is from a very, very basic perspective. To create a user for say, a new user starts in a business creating their account in AD, assigning of specific permissions to a file server, giving them relevant access to an email, distribution lists in an email, perhaps creating their basic profile on their computer, installing some basic software on a computer. But most commonly, they're not going to be leaving the comfort of their desk. Again, it depends on the role, depends on the company. But generally a level, one person is going to be sitting from their desk and answering either the phone calls or tickets that are coming in from a ticketing system. So I mentioned phone calls of somebody ringing up asking for help desk for IT support. But they also may have a ticketing system or a system with somebody in logs the ticket by sending an e-mail or they login to some sort of an IT ticketing portal, support portal. And they put in their query there around what sort of assistance they need from an IT perspective that will then get three hours or moving to a particular cue that the level one person reviews and tries to fix the issue that will do their best to fix the issue. If they cannot fix it, they will escalate it or handed over or assign it to somebody who is in a more senior position. Generally a level one person wind getting involved in server side technologies, then they're not going to be dealing with servers and networking and storage systems and things of that nature. They would escalate that up to a level two or level three. So what is a level 2 personnel Level 2, you could have very titles. Now, we're looking at a Support Engineer and IT support analyst, a desktop administrator, a desktop engineers. They could be many, many titles that sort of fall under level to level two because they're in escalated or a higher level up from a level one. Level two people generally have come from a level 1 position. I started off as a Level 1 and then over some time they built up their skills in IT, and then now have moved into a level 2 position. Some people may already be pretty technical enough where I can jump into a level 2 position straight away and skip level one really, really depends on the individual and perhaps the company as well. But a level 2 person now deals a lot more directly with the end-user or with the customer by not only providing an escalation from level 1, but sometimes now going out onto the floor. Actually going and seeing people directly working with IT, desktops, with their phones, with all of the devices, their IoT devices that they have on their desk, installing software, installing hardware, opening up computer's doing troubleshooting, installing new hardware, noisily, new RAM and hard drives and things like that into a desktop or laptop, remote management as well, so that I don't have to necessarily go to a desk. Or they could use remote management tools such as SCCM. You've got jam, you've got team viola and others, where you can actually then login to people's computers remotely. And of course they're going to be looking at the ticketing system. What I generally would recommend anybody who's in level 2 or any business you has a Level 2, level 1, level 2 sort of hierarchy is at level 2, person is the escalation point from level one. So the end users generally would not call through directly to a level, to person or a level, or our end user would not log a ticket and that ticket be assigned directly to a level to person. It would go via the level one person first. The level one person would get the ticket, will get the phone call and if they can't diagnose and troubleshoot and fix the issue or serve the requests that he's been requested of them. You will then get moved up to the level to person. We will then perform their version of troubleshooting, which should be a little bit more advanced and little bit more technical people, a lot more knowledge, a lot more years behind them in troubleshooting. To then be able to then go and assist the end user. And what's really good for level 2 person is if they're across multiple technologies from an operating system perspective as well. So having good skills in not only Windows, which is, I think is elementary, but somebody who have skills in Windows, windows 10 being the current model, but also in macOS. Knowing how to troubleshoot Windows, learning how to troubleshoot macOS, how to get these computers running optimally, making sure that there's antivirus, making sure that they are patched, making sure that they're running top, top speed. They can be installing software onto these computers to troubleshoot issues, to diagnose is used to do basic speed tests and things like that. There's some great ones available for Windows and for Mac OS. Two that I use a clean my PC, clean my MAC level to people that I know in many industries use those if you are instead, you can pick those up, running my description there. Very, very cool. And that will help people who are in a level two position. They can also be involved in some basic server administration support. So now this is not necessarily a level 3 server administrator, but a level 2 person could be responsible for some basic administrative work on Server infrastructure, logging into the servers, installing server software, diagnosing when there's an issue on the server from a very, very basic level, responding to alerts and monitoring the service as well to make sure that they're running healthy, perhaps performing some basic patching on specific service. Now the level two person, of course, needs to be a little bit more technically driven from a level 1. So having good understanding around networking, you how to connect computers together on the network, how to perform basic troubleshooting on a network. Knowing basic commands in the command lines and knowing how to ping a server, knowing how to do a trace route between a PC1 and PC2, have if a patient is having issues connecting to the network, learning how to troubleshoot and diagnosed multiple reasons why that computer could be having issues on the network. Similarly to a level one person, level two is also going to be involved with things like Active Directory. But now it's a little bit more advanced than now going in and actually doing a little bit more advanced. Things within ID that could be also involved in this have servers, so they're going to be adding servers into AD. There could be now dealing with creation of security groups within Active Directory. So adding particular users to particular security groups, granting security groups to a file server where I fall service permission structure is created. We then move to a level three. So what is a level 3? Well, we defined level 1, we defined level two. Level three is now an escalation up from the previous levels being level one, level two, level three, again, has a lot of different titles. Is this difference of the titles depending on the company, depending on the exact skill set that a level three person has. Generally, a level three person will have either a lot of skills that a level 3 oriented or be specialized in a specific area, specific technology. Within Level 3, generally you're going to find systems people, system administrators, system engineers. You're going to find network administrators, network engineers in a fine even perhaps storage people. Now we are going to be covering these from a very, very high level. But if you are interested in learning more specifically the differences between a systems engineer and the network engineer. Do check out that video right up there, where I'll go into a lot more detail specifically about those two roles. So a systems administrator up systems engineering is now going to be involved solely, really, primarily on the server technologies on servers and systems Active Directory. But now even from a high level dealing with domains, dealing with Active Directory domains and domain trusts, domain controllers, DNS, DHCP, working with building servers can be commissioning services, troubleshooting service. That a little bit more detailed and a little bit more technical than other sorts of service that may be supported under a level 2 person virtualization, managing and administrating all the virtualization technologies, VMware Hyper-V, managing and administrating all of the cloud technologies and AWS and Azure and others, responsible for backups of those servers, responsible for any virus, responsible for the security of those servers, responsible for perhaps even storage such as SAN and NAS. That could be the role of a systems administrator or systems engineer. You then also got the network equivalent of the systems guys. These are now network administrators, network engineers that now responsible for the network. They going to be looking at network switches, network routers, firewalls, security of the network, making sure that the network is configured and running as smoothly as possible that the routes it correct that network a, network B can talk to each other. Perhaps if a company has multiple sites, making sure that the network traffic can flow from one site to another. Or the specific routes over specific tunnels. Configuring things such as VPN in figuring things such as quartz, which is quality of service and just the overall network management of the entire network, that there's no bottlenecks and that it's running at its best, best performance. And then we didn't mention storage engine knee. Again, it depends on the company, but the storage person may be just solely involved with storage technologies. They're not going to be involved with just sand and Nas technologies, perhaps even backups as well. But generally depends on the company. That role can also be merged and taken on by a systems engineer or systems administrator. Well, now of course, I need to be heavily involved in data centers in common rooms, in server rooms. So going into these rooms, racking, stacking, cabling, labeling, all of the equipment that's in their troubleshooting that equipment that's in there, making sure that it's already healthy. And then of course, if, if a company has the Rome server in their own Commons room, There's relevant security in those rooms is relevant. Cctv conditioning this file systems, making sure that all of that is secure and all its ball that is running well.
3. Physical vs Virtual Servers: So we're really talking about service and server infrastructure that is on-premise well, that he's heard bothered basis for the IT managed provider of a company. We are, you know what, I'm going to talk about things like Cloud because you can have a service sitting on the Cloud or managed by other parties. For example, we're really talking about service that our in-house, they could be in your physical building, that could be in a data center or in a co-location site, still owned by the business. So we're really focusing on service, physical and virtual that are within your business. So this is an example of what a physical server infrastructure would look like. Physical servers had been around for a very long time. In the olden days, there was no such thing as a virtual server that we're all physical. Every single service that you would have would be a physical server. So physical seven, he's literally like a computer that has a lot more smarts and a lot more brainpower behind it, and can perform a lot better than your average desktop can, is physical in the sense that I can physically see it and touch it and actually go in and open it up and do all those sorts of things with that physical server. In this case, I've got an example here. A full physical servers. One is hosting a domain controller in DNS. The other one is a mail server, perhaps something like exchange occur a fossa which all of my files sitting on. And I've got a database server which could be used for multiple databases. Now, this is a standard operating structure for physical servers. You've got a physical server built that has functionality within it. So each physical server would have its own function, its own purpose. In some cases, a physical server could have multiple functions. So in some businesses, for example, one physical server could be the domain controller, DNS, the mail server, and the file server, for example. In most places you would, you generally want to split up those services into multiple service. Otherwise, you're going to be having performance issues and you have to upgrade after that. Essentially have a very, very powerful so to be able to cope with the operations. And the other scenario is if you lose that 17 I contains everything, you're in big trouble. So it's always good to look at load balancing your services across multiple service. All of the service would have some sort of storage attached to it. The physical servers themselves could have their own storage built-in. So they said a ride worth of hard drives built-in, and all of the data is sitting on that sign with the mouse over the file server, the database server that could have their own built-in storage. In the case of most, most larger businesses, you're going to have a dedicated storage device attached to it. So this would be a saint or run as a storage area network or a network attached storage. And that is essentially connected into all of my service. So the service might not actually contain most of the data. The data is actually sitting on some sort of a dedicated storage solution. Now, this seems like a very good model, but you're going to consider this is a high cost model in the sense that I've gotta have physical server for each individual application or each individual service about wanting to provide to the business. If I lose one server, I lose all of those functions on the observer, right? If I lose the mail server, I've lost my own, that could be detrimental to the business. The business may not be able to operate unless it has active email systems. Of course, the advantage of having physical service is that they physically, that they are dedicated and I can go in and upgrade them and they are dedicated for one individual service. But I do file in the era of redundancy, there is actually no redundancy built-in out of the box for physical service. As well as that thinking about costs when we're talking about things like electricity and physical Rackspace as well. The service have to physically sit somewhere. They have to be powered, that have to be cooled by a conditioning units. So if you consider all of those options, the cost of physical service is generally going to be higher than if we say look at the alternative, which would be the virtual server infrastructure. If a server does fail, for example, and I've lost my DC, my domain control MID and S. Of course I'm going to have services interrupted. Then I have to organize a replacement server, rebuild it. And if it's running something like the Windows Server, I have to reconfigure Windows Server, reconfigure my DC and my DNS. I have to restore from backups, but I'm essentially rebuilding a so after source that survive to reconfigure it, Racket, cable it up, reconfigure all of the applications and the software before it's often an operational scalability on a physical server is always going to be a bit of a challenge if I need to upgrade the resources, for example, uh, my mail server that is running 30 to eat your brand and I need to upgrade it. I think you have to power down the server source. The RAM from rubbery may be I have to white that amount of time for that rant coming off to go down to the local IT store and purchase some additional RAM, open it up, put it in, and they guard right, and then I can bring everything back up. Upgraded from 32, 64 gig, but that amount of time, the amount of effort to do that is quite challenging. If I have to upgrade the CPU, I'm maybe stuck. If, if I've got 16 cause on two CPUs and then I need more resources. I need to upgrade or double it to 32. You're going to be in trouble as well. So the scalability of a physical server is a bit of a challenge. Generally, when you buy a physical server, you want to purchase it already with enough resources for intended 12 and 24 months, even five years worth of growth, it is a challenge to look at operating those services later on. So if we compare these two, a virtual server infrastructure, I'm like the physical where I've got multiple servers hosting different operations, different services. I've got in this case of virtual server, I thought one physical server hosting multiple virtual service to the physical server, in this case, could be what's called a hypervisor. There are the big vendors which are your, Citrix and VMWare. Microsoft have their own virtualization technology. Essentially it's a physical server still running a hypervisor operating system. If we're talking about VMware, for example, the m ways hypervisor is called ES6. You install ES6 island to this, and then you would go and configure multiple VMs virtual machines within that one server. So now rather than having multiple hard multiple pages of highway multiple service, yeah, I've got the one server hosting multiple VMs. Now the great thing about this, if I do a comparison, let's add what the domain controller in the physical environment, heme. And it has ran and it has one CPU. If I need to upgrade that, I would have to power those services down, open the box out because that additional hardware and install an additional hybrid if I can even upgraded in the first place. In this scenario, this hardware, the server, has got the races already built in. So you would go and purchase this hypervisor, this physical server, with enough resources to be able to cater to all of this and then some more intended growth, right? So if my DC now requires more resources, I can literally upgrade the race horses on he using and physical resources that are sitting on my hypervisor up. So I can easily boost up the RAM, the CPU of any of these directly using the resources from my harder for my hypervisor. So essentially a chunk of RAM, let's say this particular server has 64 gig of rent physical 64 gig of RAM. I can allocate components of that 8, 16, 24, 32 gig of RAM, for example, across these vigils. And it's going to use 32 gig of RAM physical on my physical server. Besides the CPU, the CPU can be shared. So I can use the CPU that is unhappy and shape components of it across my virtual service. Now the thing that's very important is when you are speaking up or scoping out your virtual server infrastructure is you got to think about capacity. You're going to either think of it, hi, going to provision those the end that he can under and over provision VMs. You don't want to essentially create too many VMs in here that they start to run sluggish. Because what can happen is there are, there are operations in place yeah, for sharing CPU resources in usage. Where if this bar here it is, which virtual server hogging up or taking up most of the resources and the other service could potentially perform poorly as a result of this server using up most of the resources. So you always have to speak up and allocate the resources accordingly on your physical server across your virtual service. So straight away you can see that this is a lower upfront cost model. Rather than me having to purchase full service. I've just purchased one and I'll be sold at multiple virtual service on top of it. The maintenance of the soma is significantly easier as well because I've got less of them. If I have to go and maintain all of the surveys, routinely going in and checking and making sure that The renewing the warranties up reading the pods, updating firmware, all those sort of things. I wouldn't do it across all of my physical service if I've got hundreds of them, that could take a long time compared to a hypervisor or a physical server running virtualization technology. I do it essentially on the less infrastructure. The only consideration that you need to make is when you're choosing one or the other as well, is the compatibility of the applications, all the programs that are running on that physical server. And there are still some services that can not run virtualized. And that is changing, is changing very, very quickly. But just keep that in mind and look, I'm going to say that majority of your core and services are going to be able to be run virtually. So you don't have too much of a consideration then, but do double-check if you are running third party applications, potty applications that may be tight and just for your business or is not very well known in the industry, can see that whether they can actually run on virtual service as well. Ideally, when you're sitting up things like high availability and redundancy, you don't want to have just one physical server here. I'm running virtualization technology because in the case of this, if in the physical world, I lost one sever, I've lost 17. Services could still potentially still operate. In this scenario. If I lose this physical server, I lose every one of these virtual service. So what you do is set up multiple, at least two physical servers, set them up in redundancy so that I have high availability. So services can flip between the two. So I can have a second hypervisor configured between them. They connected, they're what's called highly available, high availability. So there's the technology and configures and the two service know about each other. And I can have the service split across the two. So I can have, for example, I can turn the day, say often him, uh, be running it over. He. And I can actually split the services, all the VMs between the two service. In the event of a disaster and a physical server die, the psi dot server died, right? All of these VMs could be spun up over here. So in this scenario, I lose a setup, I'm in big trouble. I can't really get anything unless I restore it. I've to build any set of potentially restore the software, restore the backups. In this scenario, I lose a server. I can have everything is spinning up and running on the secondary server right here. If we're talking about much bigger picture, if you lose, if you lost both of them, if they both like head and saying the same data center in the same columns room, you can set up multiple servers across other locations and then have them replicated from one side to the other. So that in the event of a disaster and your operations do file, you can easily spin them up in another location. While in the olden days, in this physical server infrastructure, unless you've got it configured properly. If you lost your on-premise service, if you lost your data center, you'll comes regular server and you can lose everything. And then to be able to restore everything could be a huge challenge and could have a significant financial costs of the business. So as you can see it really in the scheme of things, virtual service, definitely a better option for, but for most businesses, you're thinking about cost-effectiveness. Performance can be improved because I can easily increase the performance of these VMs quite easily. And disaster recovery is much easier as well because I can have services such as high availability configuring services file and one that can fail over to the other. So the things you gotta consider when you are looking at physical or virtual and comparisons between the two is really you starting off with the budget, right? You're starting off with how much is it going to cost me? How much physical hardware do I need? How much is that going to cost me in terms of procuring the hard way, setting it up so and maintenance, somebody physically going out and maintaining it and building the server, right in a scenario of let's say, of an IT professional and have to go and source IN particular piece of hardware. And you either they could do it in-house or organize a third party. But you have somebody needs to physically set up a server in a virtual environment, spinning up a seventies, considerably easy. I could just literally I virtual server that's already sitting on some form of physical server infrastructure. Consider your disaster recovery and business continuity. In any business, you want to make sure that services are operational as often as possible and not in the event of a disaster, in the event of something going wrong, you can restore operations as quickly as possible. Restoring operations in this model is much easier and much more timely. Like you can actually restore things in a much quicker fashion. This model is a bit more challenging. It can be done effectively if you are willing to put an invest the money and you have full replication set up across multiple physical service. Virtualized disaster recovery and business continuity is a lot more consistent. So remember that if you lost a server in this environment, That's seventies to be rebuilt in this environment, you lose it. If you've got high availability configured, it just spins up and runs on E and you potentially have no to little as each little could be only a few minutes while the server is booting up again. If you lost everything, you're in big trouble. If you lost everything he it could be haven't replicated over to alternate sites. You lose this. You can spin up everything over he quite easily. So most surface will have some form of backup in place. He's actively reviewing BI service and backing them up on a regular basis, whether it be daily, weekly, or monthly, always have to then go off to ice, some sort of a backup media and retained for a certain amount of time, et cetera. But in the event of a server to server dying, I've to restore everything from scratch. You can take a long time. It will take a long time if I have to procure the new hardware and ever and everything, if I lost a mail server, like, let's say this is like high, but I've actually lost a virtual server. The restoration of that video seventies a lot quicker. Also, in a virtual environment, you can do Full snapshots of the VMs themselves. Essentially, the VMs are just a big file containing a lot of mini files that resides somewhere. So restoring I virtual server is much quicker and more effective than a physical server. Performance is the other consideration. Purchasing some hardware for your physical server, then purchasing a hypervisor and adequately specking out your virtual service and you can have adequate performance right now down the track as your server acquires better performance, we need to improve the performance. It's more challenging to do that physical side than it is on Virtual WAN virtual you can just literally spin up that VM and just give it more CPU, more ran literally on the flight. In some scenarios, you may not even have to power down that VM to do that. Sorry, it is much more adequate and much easier and so much simpler in a virtual infrastructure as well. And then let's think down the track. Let's say you need to migrate services. You're changing offices, you are acquiring a new business or you've been acquired by business and you need to migrate services, or you're running an old operating system and you need to migrate services from one to a new operating system, for example, whatever that scenario might be, migration of virtual service ease, easier than migration of a physical server. In a scenario of hea, funny to move service from one to another. I literally can just move them on the fly from these hosts to this horse. I can procure a new piece of server infrastructure, physical server, and fragile and sit up here. And if I need to move VMs from here to here, is essentially once that's all configured, I just right-click on it and I can move it on the fly from one to the other. I can't really do that on the physical infrastructure. If you're changing offices, a virtual infrastructure, I literally just pick up that hypervisor, one physical server or the multiple contained by multiple VMs. And I just really like hate them. In the physical. There's obviously a lot more, so it's a lot more effort to move things between one side to the other. So that is a overview of physical and virtual. So really in summary, physical, you're going to have to have physical pieces of hardware, physical servers running multiple different types of applications. While in a virtual infrastructure, you can literally commission one or more physical servers running hypervisor technology, and that had multiple virtual servers running within it.
4. What is a Server: Essentially a service, it a voice that is a lot more powerful and ascended and use a desktop or laptop computer. Generally, the comparators inside the server will be very similar to what you find is our standard desktop or laptop, but a lot more higher-end. You can also add a lot more resources to a server. You can also have hour of additional source of cards or peripherals that I stated desktop or laptop would not have. As surveys generally going to be used in a corporate environment in a business. You might have uses to do some service testing at home. If you want to be doing some, you know, you're in lab urine learning as well. But essentially a Rack Server is going to be sunlight is going to be connected into something like what's behind me. This is IRAC. I cabinet were essentially it's a place that stores servers, switches, firewalls, storage unit first sort of things. And the fact that it's called Rack Server means it's going to be racked somewhere. It's not going to be like a tower device, like a tower desktop or a server that sits on the flow of, sits on top of something. This is actually going to have some rails that connects to the side of the server. And then it's actually going to be riled and rack into something like this behind me as server can be configured in a number of different ways. What I'm going to go into detail of the different types of service that we have. Different videos that talk about the different types of faults service such as file server, web server, DHCP server, DNS server domain controllers, database service. There's a whole range of different service, but really the end goal is to service something, to service the end users, to serve as an application, to serve as a website service, whatever it may be, essentially is going to be set up to have a particular server function to be able to provide a service to some end, end device or end user. So this is a rack serve up. Essentially its main purpose is to go into a server rack into a data center. So I'm going to just sit like a normal Tower server may say it's a full length server which will require rails on either end on the sides on the left, on the right, and then wrapped into a server cavity into a rack cabinets. This is a one IU server, essentially taken up one rack space. And it's a quite sleek looking device. It looks quite nice. Obviously the fronts of this is just a cover to cover that's covering the internal components or the front components of the actual unit. Easily lockable. So there's a little area here, we can just lock it so that you don't econ actually take this off. But you can easily just remove the front of it by just clicking this little knob, little latch, and it just comes off straight like that. We've got the unit, this particular unit doesn't have any hard drives inside of it because we are connecting this to a ES6 I farm, to a VMware ESX I farm. And it's connecting to a storage device called a sandwich has all of my hard drive. So the back of this unit is quite simple, being a one RU unit. We've actually got limited peripherals that we can put into this unit. We'll see that at the top, there's a couple of slots available, so I can actually add additional cards if I need to quite easily by opening it up for moving these slots. And then I can put it in the same way as a normal pace. See, we'll just go through some of these poets. So here I've got an, I drag polar. This is essentially a management port where I can running to an Ethernet switch and then access this whole server remotely on the network. Got a COM port, I've got a VGA port, but a couple of us space here. I've got my Ethernet ports. This is going to be y one gigabit Ethernet and then a couple of slots before 10 gigabits for SFPE. And then a couple of powers here as well. We've got two of them for redundancy and high availability, because obviously we don't want power to go out from your server itself. So we always set them up in pairs. These would be running into two different power sources. So one into one power rail or until you different UPS than the other one. So that if one power rail, one PDU when UPS goes down, I've got access to the other one and gives me power. These are easily removable by pulling a little LacI and the whole unit just comes out like so. I will buy a brand new one if a particular unit guys, and then just slot it in as normal clicks right into space. Essentially these rails are what's going to be connected into your server cabinet and also into the side of the server like this. So you'll see that the rail itself moves left and right. So you're going to connect one of these into your server cabinet. And then these little notches on the rails match up to the notches on the side of the server. So here we've got the inside of the unit, so I've just taken that cover off by unlocking it and just removing it. And you said that it is quite a detailed piece of equipment. So the fans will keep all of this unit stuff he called and the whole server itself called. These are the RAM slots, okay, so the ram is going to be inserted right under H0 and then your two big heat sinks for your CPU. So this is actually got two separate processes or what they call sockets. A socket where your CPU is going to sit on top and then your big heat sinks on top of those CPUs. Inserting RAM is quite simple. You literally just click on the little tabs here, on the side. Plastic little slot comes out. This is really just to protect the actual groove of where your RAM sits. And then your RAM would just slot into place to insert some more ran the same way that you do it on a normal PC. You probably your RAM and use flawed it in. Where you're going to need to do is you're gonna need to pull these levers up left and right. I should remove this cover to be able to access the RAM slot on this side here. So here's a couple of power units and from the top got a couple of other peripherals where I can connect additional functionality into. Here's a, here's another riser, essentially allow me to add other cards. Can remove this by lifting this tab up, the whole unit just comes out. I can add additional cards into here. So as you can see, it's laid out very, very nicely, is actually quite nice and quite packed full of features. So we're here now inside of our columns room because there comes cabinets. We are going to be racking the unit. And you'll see that I've just got a number of slots here. Association, I'm going to touch the rails on the left and on the right. And then once that he's in on the front and on the back of the unit. I can then slide my device in as normal. And then I'm good to go OK. And then it connected, I can connect it into my particular, to my particular switches, into my particular powers on my left and then right. And then get that on the network and go ahead and configure it and then use it. So here's an example of a device that is rats. So you've got the cabinet right here. You got the rial that's hooked up into the cabinet. And then you've got the actual system itself, which is connected to the rail. We saw the top, this is the actual unit itself. And then the rail runs all along the side here and it's actually mounted into the actual side of the system. Most units will either be to IU or one IU or more depending on how big it is. This particular unit that the example that we're looking at here, this is a two IU units to saying enough to rock units faces. I wanna, you would essentially be half of that space. And you see that right here. It's actually going to be clicked into one spot. But he's capable of taking up to the two ru. So obviously whenever you're racking one of the systems, you want to make sure that you've got enough capacity, enough storage space to be able to accommodate other the one Ru with a two-year or largest space.
5. Comms Room and Datacenter introduction: So organizations throughout the world store the network equipment in different sorts of places. And it really depends on the size of the organization. If you're in a small or medium or large business, the equipment is going to be stored in a different place, in a myriad of different sorts of places. Sometimes a small organization may just have a server and a network switch to sort of sitting on the side of a room. Generally not a good thing. Some may have it in a little cabinet that's mounted to the wall, or they can have a cabinet that's underneath the desk. Sometimes I may have a big rack inside of a room. You're going to have cams cabinets, you're going to have server cabinets. And then in a larger organization, you may have full rack rooms, rooms, and it just dedicated for server racks, for networking racks, and for all of your networking equipment. So companies will generally have this equipment, I thought, on-premise. So on this side, they could have it in their office. They could have it in one of these sister offices, the parent offices, wherever it might be, but it's on the managed environment. Or they could have any night remote data center. So it's hosted by somebody else. So depending on whether if it's small, medium, or large, the setup of where that equipment is going to be stored is going to be different. It could be the dedicated room in a dedicated closet, in a dedicated big space, maybe on a flow wherever it may be. So that's equipment that is stored on premise that is equipment that is stored within the office and under full Office Management. Now it's very, very common that companies, regardless of the size, may actually have equipment being stored it by third party providers. This could be perhaps a third party data center. So this is a data center, is essentially a big space that is dedicated for storing of networking equipment. So there are lots of these around the world, hundreds of these around the world. I mean, if you think that the big guys, your apples, you're Microsoft's, you Google's these companies, but their own massive, massive areas that it just decked out with just rows and rows and rows and flaws and flaws of data centers just covering a massive acreage of space, a company may engage one of these third party data centers to be able to store the data with them, to be able to store their equipment. Essentially, they would go and actually rent out or lease up a specific area in this data center. It could be half or act could be a full rack. It could be many, many racks. And then you pay like a monthly or quarterly or an annual Fe to that third party data center provider. They provide you the backups. They provide you like the backup power they provide you the redundancy. Then show that all the technology is set up correctly with data that is, there are different tiers as well. The higher the TEA, the better quality that data center will be and the better risk rating and the backups and redundancy and electrical and all of these other things that sort of come in different tiered data centers. But essentially you are leasing out that space. So they actually go and put their service, they switching the storage, they firewalls, all of that in this third party data center is still be managed by the company, but it's now off-site at a dedicated data center. So there's various different configurations available because then of course on top of all of that, you think that the clad, you've got your big providers, your AWS or Azure or your Google Cloud, who themselves have data centers all around the world, but that is now on the Cloud and you don't really have the same physical access to those data centers. You're going to see just the software side. But of course that's all sitting on physical data centers somewhat. To the next video we're going to now look at a data center. Here's what I dotted into may look like. They come in all shapes and sizes. Some very, very basic, some very, very modern, some MOOC really cool. Some look really, really dingy, depending on where they are.
6. Datacentres, Server & Comms Rooms small: Data centers, server rooms, chromosomes. What are we talking about when we're talking about all of this now? The two most common places where your IT systems are going to live. So you have servers, storage, and all of your networking devices, all your security devices, all of that is going to live inside some form of columns. Cabinet, like a big cabinet or rock that has goes by many names. I cabinet where you are sliding in all of this equipment. You're racking all these equipment in your cabling and in your drilling it, in your clipping it into it a little mounts, whatever it might be. This equipment is to sit in that course in a cable and as I said, and it needs to be running and communicating with each other. These cabinets or server racks need to sit in something. So generally they going to be sitting in some sort of a server room. All right, combs room or even in a data center. Okay. Now what are the differences between all of these? So it really depends on the company set up, the company structure, that company size. So a smaller business, let's say it's a very small business, perhaps there's 2030 stuff. You may have. Not necessarily I full server room. You may not have an actual room that he's dedicated, server equipment or networking equipment. You may have just a little cabinet on the side of the corner of an office, perhaps in a cupboard somewhere. A little cabinet containing some of the core equipment in there. You're going to have something like your route is your firewall. You might have a server or two and perhaps some sort of backups and some UPS which is useful. Your backup redundancy of your backup power. And that may be it's a large or medium lodging business. May actually have a dedicated room where you actually have a room that you swipe in to some sort of security. And then you'll into a room that has potentially one or more cabinets within it. And each cabinet contains relevant infrastructure. Now, depends on the environment, depends on the setup and depends on the amount of equipment that you've got. Each cabinet generally will have a specific purpose and it's going to be laid out in a specific way. So it's very uncommon to have networking equipment and server equipment, and then storage equipment, and then the next cabinet, the same networking servers storage and have it all sort of mixed up generally, especially if you've got somebody who likes to design things well and make sure that it's neat and tidy and things is sectioned off. You might have a cabinet that is more network focused. So a cabinet that contains perhaps patch panels, which we're going to look at in a little while. The patch panel essentially connecting your switching, all of your devices are running into patch panels on ports on the walls across your office. It might have switches in this in this cabinet along with the patch panels. You could have your firewalls in there. You may have some other networking devices in there as well. And that's maybe just the full extent of that particular cabinet. Another cabinet could have your server equipment, could have some more physical servers in there. And those physical servers in turn are running virtual technology, virtual service for example. And then he could have an observer where you've got some storage and other Cabinet. We've got some storage. You've got a big sand unit or some nasty units. These units could be connected to UPS's, essentially get all of the stuff powered up and redundant on Palo, that the fronts of the units, the back of the units of the front of the switch, the front and around to the front, to the back of the devices. We've got the cables coming in. They're going to be running specific areas. All of these are going to be cabled tied. They going to be needed, they going to be labeled that go into specific areas. Now, all of that would all reside within these server cabinets, within these racks, inside of a server room, or inside of a small cabinet that you might have scattered around the building or in a specific location. Then you've got something that's like a data center where it's essentially largest scale server room or data center generally will house a lot more infrastructure. Now, again, it depends on the company. Some larger companies may have their own dedicated data centers. Essentially, it's a massive space. It could be a whole floor or several floors in a building that is just full of networking and server infrastructure. Essentially, it's just a massive server room. Think about it as a massive server room would be something like a data center. And all of this stuff is all decked out with state of the art redundancy, power distribution, monitoring, cctv, fire protection units so that if there's a fire and it sucks the air out, it suppresses all these sorts of chemicals. And it's just that there's some really, really cool stuff. These rooms as well, datasets is even on server rooms. Generally will have like a raised floor as well. Or it could have something on the top as well. So if you have a rice floor, perhaps cabling is all routed underneath the floor. It's also good for maybe dispensing of water. If there's flooding, it goes under the ground as opposed to sort of flooding the equipment. Or they could have titling on the top. The layout and the setup of data centers in general really vary depending on the data center itself. So you've got data centers that are sort of owned by a business, that is their data center. Some businesses may have their own dedicated data center outside of the office. So for example, there's a large company. So let's say Apple's headquarters, for example. They have their office space and they've got separate data centers where the apple infrastructure is house and it's sort of a separate environment because you don't want to impact both environments, you what they want to keep it separate. So that's a data center that would be say, owned by a business. It's their dedicated data center. Then you've got what's most commonly used in a lot of businesses is you've got shared data centers. Essentially, it's a data center that a third party company owns and manages and you rent or lease out a space in that data center. So you could lease out a whole row of server cabinets. They now become your server cabinets that you hyphal every month, every year? I certain amount. Those cabinets, of course, because it is in a data center, are done to a particular tiered level. So data centers, but we won't go too much data, but they have different tiers. The TIA depend determines how how redundant that data center is, how good it is with keeping the systems up, up, up running, fibers, fire suppression, staff, security, all of these sort of things. But if we go back to what I was saying, so you've got full racks and racks of of server cabinets that you lease out, and then they are yours so you can go in and give me security passes to enter the specific facilities. You'll have access only to your racks. Now these wrecks could have keys, they could have a form that you swipe, could have fingerprints, could have retina, could have a lot of these coal, bio sort of technologies for you to get access to just the racks that you are leasing or borrowing. You could also purchase those racks and then they become yours, but then they part of a larger data center. Commonly these data centers that at least that I have multiple companies leasing them. So your racks, your ten racks that are managed by your business, could be sharing the 10 next to it from a different, completely different company that's doing their own completely different thing. So you're going to be interacting potentially with other system engineers, with other IT professionals from other companies. So that's quite cool as well. We can share stories are already running and what are you running? Of course you want to be secret about what you're running because you don't want to be letting out the Cyber Security secrets of your setup, of course, but that is one of the cool things about datasets. You get to interrelate with other people. And these things can be huge, they can be very, very large, multi flawed, and data set is just amazing. So one of the videos in these next few videos we're going to go through just a little bit of a tour of what a data center looks like, sort of give you a bit of an overview there. Then we've got the Cloud. So what we've been talking about there is all on-premise, right? Even if it's On-Premise in your office or it's On-Premise, Data Center will classify that as on-premise to some extent, even if it's an a remote data center, then you've got the cloud technologies, of course, when we're talking about the big guys, which would be Amazon's AWS. You've got Google Cloud, you've got Microsoft Azure as well. These are all cloud-based services where you pay these companies for a space. There cloud-based service, Cloud-based infrastructure, cloud-based storage. But it doesn't sit in just cyberspace, right? It's not just adding the clouds. So really in the cloud, these companies, the actual infrastructure where your stuff is sitting is actually in a physical data center somewhere. So for, for you know, for all you know, for example, a data center i physical damage you may know about. You may have some infrastructure there. Perhaps AWS is also leasing a space in that data center. And your actually in a data center where there's a whole room with AWS owned servers or leased service by AWS. And it's AWS's and it's just physical infrastructure that is managed by them. So during the day, even if it's a virtual server, of course, is going to be physical somewhere. Even if it's a virtual server in the Cloud, it's going to be sitting on a physical server, on some physical storage, on physical networking is all the data in and be traversing through. To some sort of physical data sets up an infrastructure somewhere in the world. And of course, what you'll find is if you're talking about the Cloud and you're talking about AWS and Azure and they sort of companies. You've got regions, you've got availability groups by the ability zones, I should say, where? Australia, if you can tell from my dodgy accents, my zone in Australia would probably be somewhere like in Sydney. So AWS, azure, Google, google Cloud have data centers in Sydney in other parts of Australia where that data is sitting. So that's what that's how I know where the data physically is. It's not that it's just sitting somewhere in Australia. It's actually sitting in a data center that is physically housed within Australia. But look, we can talk about this. A lot more. Data centers are awesome if you ever get a chance to go and visit one, do that even for a two up there. Amazing, especially some of the big ones. Lot of cool technology there. So that's an overview around data centers, around server and comms cabinet side. And here we are inside of a data setup. So this is a site where especially computer equipment lips. So there are actually happens configured the cabling running on the top. How are rather as fiber and Ethernet cable and other commitments. I'm running into equipment located inside of these cabinets. So you can sort of say there are devices, there are service, whereas network switches and routers and other bits and pieces storage devices running into cabinets like so. For every single data center would be slightly different. Some will be laid out to others. To this particular data center is different cabinets depending on Watson services are watching the company is running into these particular sites. You see here the number of cables and connections running into this particular data center. These cabinets themselves will be kd, will be protected. These particular ones will have a standard cave. The more upper model converges. Swipe project with swipe that could be fingerprint ones as well. We get access to your actually wraps via those more advanced security measures. Say either this one, for example, you've got an all water cabling running out from the top of the device properly catholic to the worry. And that will then expand running to a different cabinet or radically straight. The absence of other rooms in a data center or into an alternate location for the other. Tables could then regenerate unsharp running around trays like this on the word, alright, avery cable tied together and running continuously for my patients have your own. These are cisco switches, that 10 gigabit switches. And you see that all of my blue cables, which are all my data cables, are running right into this particular switch, which then connects to a number of services to get me into the network, essentially network connectivity. So here we've got the back of the switch. So obviously with all the cables running into the front from our patch panels, switch itself has jewel powers. One going to the left, one going to the right. So in the event that I have a power outage, in the event that I have a house supply go down, I've got a second one that continue operating. These particular switches are set up in what's called a stack. So they've got propriety cables that are running from one switch to another switch and actually seen as single units. So they're actually stuck in one big group. So here we go to server. This is a rack mounted server. You see the brain is Dell EMC. So you've got a traditional computer which is your standard laptop or your desktop in this case, this is a wreck mountable server, which is actually spread into this particular rack. This is what's called a two R u, which is rack unit server. So this is a tendon to the size. A one IU is generally half of the size and it just really indicates the size or the actual lab and the height of a particular recommend to device or every recommended device will have a particular are you wreck unit number associated to it. So if I just open this thing up so that this is just really just a fancy computer. It's got a number of different hard drives inside. It's gotta send VGA ports for the display to let me know what's going on. I compare it on and off. It's got a CPU, it's got a RAM, it's got some other internal graphics card, etc, etc. Lot more strong than a standard desktop computer recenter, the laptop computer. So there you go. That is a server. And then obviously to the back of that, that is then connected into a switch, which is what we saw before. And then given network access as normal, here is a, another work them server, another tool I use server. This is a thing such as is done by IBM slush 1 over 2 is a couple of cis 1.2 terabyte drives. This particular server is acting as a forest for here 65. This is VMware's virtualization environment to see the front of the day, but a couple of USB sticks, that's an LED indicators linear, what's going on in the universe. Serve as another device will generally have your cow is as well. So that if the left one goes down, if this power supply dyes certainly doesn't actually broke down and still be operational because it has to. Now suppose running animate is in turmoil and running to a left and right. How on board or power supply? My own, how rapidly to the left and right of the cabinet. And in turn that we're running. So your backup power, vacuum, you serve as you've got the pavement which we are running into switches. And then you sit at the server itself has a number of slots available, work and add additional cards, peripheral don't cards into their thought. My Ethernet ports for gigabit, etc, etc. We will remotely controlling it, not storage units, right? So these are all just pulling disks. Essentially pull these out and start putting brand new disks in here. And they get everything nice and juicy tender capacity is an example of a smaller lower in NUS. Describe brain called phenology essentially is just a rack mounted device for storage. So a number of hard drives you see there's all these hard drives connected. You can then get multiple arrays. Plugin underneath is to expand your storage array. So knowledge is one brand you've got other ones like cleanup. And then if you go more enterprise and got lucky delhi MCs, you've got NET Apps, you've got other larger scale vendors that can do some pretty cool storage, SAN and NAS capabilities and they can be expanded pretty significantly. So in almost every rack set up, there will be some form of firewall where that is built-in via a router acting as a firewall or dedicated firewall. So in this case, we've got a brand called Fortinet. We've got a couple of different firewalls for redundancy. So if one firewall goes out, the other one can pick it up, setting a high availability setup. And essentially all of my traffic will flow in and out via these firewalls, a follicle control, the security, what ports, what traffic, what IPs are allowed through it. And then from here it will then direct the traffic over to the Internet, over to my links to a murdered him out to the Internet, for example, or directly out into the street or into an alternate building. So other brands of firewalls would be your Cisco. Asa is you've got Jennifer's as well. You've got soft phos is a whole bunch of other brands as well that do some pretty high-end firewalls are at the enterprise space. To do that, power is fed into Haiti US, right, is essentially a power distribution unit. You see all my powers are running into the one side. He similar one on the left side. And the names would then be similarly going into different phases, into different power outlets, coming into my building, Harris and distributed as like so. Here we've got the back of the server cabinet. So these all indicates the plugs where the actual servers are going to be recommending to the actual switches, routers, etc. are all going to be railed against this and then screwed in different servers. And what difference connect us to be able to connect into these units so that I can easily racket devices directly into the cabinet itself and keep it all nice and neat. Enterprise grade industry standard. Ups will generate a type of years. He says, look back on our privacy when you create your watches like godlike, sorry for running a concern. All of your power. The powers of the chocolate for generating today running into various big UPS's, those big generalities that we've saved, your backup power development. How are the actual individual metabolising cells? So there you have it. There is a basic overview of a data center and sort of the structure and how the data is sort of laid out.
7. Servers and the Cloud: Hi, welcome to this next video. Let's talk a little bit about service in the Cloud, right? So we've got a good understanding now that you've got service that can sort of sit in various places, you've got physical service where you go down to your local computer store or you distribute out whoever it is that gives you physical servers. These can be ranked based servers, these can be serviced that blade service, that could be tau, a service, that could even be a standard desktop or laptop PC that is acting as a Service. You're installing server software onto them. And then of course, you've got the cloud. You've got cloud services that are sitting in the Cloud somewhere. Now, the big ones, the big players when you're talking about Cloud Service or Cloud infrastructure specifically are of course, AWS and Microsoft. Google also has their own stuff, but I primarily stick with Microsoft and AWS, which is Amazon's AWS or Amazon Web Service. And Microsoft Paint, Microsoft Azure as yup, however you depend however you want to say it. So these are if we're talking about service specifically, there are servers that sit in their infrastructure, right? So you could have wherever you're working, if you're looking at getting a job, you're working in a job right now. You could have servers that are both sitting on-premise, which you call on-prem or on cloud, on the cloud or cloud based or cloud hosted. And they're going to be sitting on generally one of these three, AWS, azure or the Cloud, google Cloud, but there are other services out there that are also cloud base. Now of course, the servers that are sitting on the cloud generally going to be virtual service, right? So we talked about physical servers and you talked, we talked about installing some virtual operating systems. So you've got VMware and you've also got Microsoft Hyper-V. There is a sort of software technologies that let you install virtual machines on top of physical infrastructure, service in the Cloud. It's really the same. There are virtual VM's, virtual machines sitting in, let's say AWS, you could access to what's called an EC2 instance, which is an AWS technology. And that is sitting within this VM and ACE2, a VM itself. And that in turn is sitting on some physical infrastructure. And this is the great thing, is most people don't think about it this way. That when you're thinking about AWS and you think that mocks and all these big guys who have cloud-based computing, there's actually some physical server, storage and networking. Someone out there. It's all configured. It's all configured for you. And then I just essentially lease or loin a bit of that physical server space for you to use and install your virtual machine within it. Now a lot of companies have got birth. They'll have on-premise and they'll also have Cloud. This is what's called a hybrid model, where I've worked across many, many different companies, many, many years. I've always seen hybrid models. It's very, very rare that you find a company that is 100% on the Cloud. They do exist, but it's not that common. Most companies will have a hybrid model where they'll have both on-premise or physical servers with perhaps virtual machines installed on them, and then other virtual machines that are now cloud-based. Now of course, because it is Cloud-based, there are pros and cons, of course, right? If you've got a VM sitting in your company where you work, or perhaps where you want to work. And that server goes down responsible, you lose that. You need to get it back up and running. If it's sitting in the Cloud, they're responsible for it. I mean, you sort of are in a way because you you manage it and you paying for it, etc. But they're also responsible because it's their infrastructure. And what you'll find is when you have your service on-premise, you need to make sure that they're always up, that they're secure, and that they've got backup power UPS is always sort of stuff all configured so that if the sighted side there is a power outage, you don't lose them. Well, if they're in the Cloud, then Amazon, Microsoft, Google, they're responsible in a way for keeping your server up and running. So that's why you pay them. Because you're insured more by uptime. They have like a very, very good percentage of time where it's very, very rare that a server will go down on the Cloud. It does happen. They're not a 100 percent foolproof. But there are so many levels of what's called redundancy that Goswami levels of high availability where if one thing fails, this thing picks up the slack and it doesn't file actually because it's just sort of this course, then this one will still operate the server. And then if that one goes is still something else that can still make sure that the server doesn't go down. So the cloud is brilliant because of that, because you are paying for a service that is more reliable. And, but of course, the thing with the Cloud as well is that you need to now learn all these new technologies. So if you're familiar at all with on-premise technologies, you're familiar with different sorts of servers and the different technologies around the service. The eye pays, the networking, the DNS, dhcp, all of that sort of stuff. Well, on the Cloud, they have their own technologies. There are names that are in everything that is sitting in the Cloud that you now need to learn and understand. It's something completely new. And if you look at AWS, if you look in at a zoo or even if you look in at Google causes, there are certifications that you can go and get to become experts in those particular fields because that is a whole new world. So just because you are an expert with servers that are on-premise, doesn't mean you're going to learn and be an expert straight away with the Cloud-based technologies, you will have to learn some of that. That is a bit of an overview. You can go into a lot more detail around the cloud. The cloud is awesome. More and more companies are going towards the Cloud. What we're going to be talking about in this series is the foundational stuff, right? We're going to be talking about the foundation stuff in an on-premise, on-site environment. But you can use all these practices, everything that you're going to learn in this course can also be used in the Cloud. So nothing here is going to stop me from understanding at least the basics to then give you a better foundation when you do want to implement more Cloud technology. So it's not one or the other. This is the foundation stuff that you need to know that can then be used in a cloud when you are configuring all of your Cloud technologies.
8. Top Server Functions: So let's now go through this top 20. We'll go through them really quickly. Give you a bit of an overview around each of these and what they are. Number one is a file server, a very, very common server. A lot of companies will have these. And it's essentially I serve up that is for storing files and folders. So you're going to be citing business data, documents, images, whatever the actual company does is going to be stored on a file server or a fleet of file servers. And then these file server is going to be accessible on the network for people to connect to it. So commonly, if you are working in a company and if you're running on a Windows computer, you open up your mic computer, your file explorer, and you've got other drive you have, of course, your C drive, which is your primary Windows installation. But then you might have a G Drive and H drive and F drive as then drive all these other drives. Most of the time they're going to be pointing perhaps to a file server of some sort where that particular, you know, if you're in marketing, if you're in sales, if you're in finance, that could be data that is relevant to that department and it is stored on a file server. Commonly, a file server would use protocols such as SMB, NFS, as well as common. It could be on a Windows-based file server environments, could be on a Linux Space File Server environments. You could even have a nares, which is a network attached storage, which is acting as a file server as well. Second one is what's called a domain controller. This is almost like the elementary server to ensure that your network and all of your servers and all you need to buy your devices, laptops, desktops, Mac, PC, Linux are all communicating within this environment called Active Directory. And Active Directory is stored on a domain controller. So you'd build a Windows Server. You then go and install a domain controller role. You then go and have all of your Active Directory tools where you manage all your users, your permissions, what people can and can't access that computers that are bound to this thing called a domain is all managed within a domain controller. Within the domain controller, you also have things such as group policies that are essentially allow you to push out policies to a fleet of computers on your network, not just desktops and laptops, but also serve as making sure that the passwords, for example, are complex. Perhaps you want every computer on the network to have the same wallpaper, the same screensaver. Perhaps you want to disable right-click, you want to disable access to control panel. All of this is all controlled by a group policies on a domain controller, you think got a DNS server. Now commonly a DNS server will also sit on a domain controller as well. If you are in a larger business, you may have multiple DNS servers. And of course, DNS is going to convert your host name. You're fully qualified domain name, which is a FQDN, to a IP address. So the whole DNS server controls when you ping a particular server, when you ping a website, when you ping whatever it is within your organization via a normal host name or FQDN. It then we'll resolve to an IP address. You can also do reverse lookups on an IP address to go and resolve against the host name. But this is almost like the address book for all of your IPs and for all of your systems on your network to sort of resolve between each other. And before is your DHCP server now computer on the network, how does it get an IP address? Well, commonly it's going to be plugged into a network, is going to be connected to a Wi-Fi device, is gonna go and scan your network and ask for an IP address from something called a DHCP server. The DHCP server manages all of your IPs for all of your devices, and then pushes out an irrelevant IP address to a compute up to a survey out to a Internet of Things and IoT device, whatever it may be. And it gives it perhaps not just an IPA, but also the route up the gateway address, the DNS addresses and other information as well. A web server, of course, you could run a website some place that is stored on a web server. You could have something like Microsoft's IIS, which is common with the Windows server fleets. Alternatively, you can use something like Apache. You can use PHP, and you can store that on there. You could even run things such as WordPress or Drupal or other sorts of web applications on a web server. Web servers and other servers will communicate with something like a database server. Perhaps a database server could be running something like Microsoft's SQL. It could be running Oracle, for example. It could be running MySQL as well, which is a free version. And it's essentially just a database, essentially thinking about as a big repository of information and a website and application. Something on your network goes and queries your database to retrieve information. The database is almost elementary for a lot of applications and websites nowadays, especially when you're looking at hundreds and thousands and thousands, perhaps millions of rows and cells that need to be contained in a centralized location such as a database, an email server, most commonly being something like an Exchange Server. Nowadays, these may be a little bit less common because a lot of companies nowadays are going on the Cloud and the using the Microsoft 365 services essentially exchange on the Cloud. But a lot of places still do have some form of a Internal e-mail server, whether that be exchange, whether that be some sort of an SMTP service or a relay or something like that, but something that he's hosting e-mail services or at least managing some sort of e-mail mail services within a company. Application servers are a very broad term, but an application server can install one or multiple different types of applications. These could be apps that are specific to your organization, that they may have been developed in house. They use just by a particular company and they're not use anywhere else. And that's application you stored on a server and that server becomes an application server. There are other apps that you may have, other third party applications that are installed on an app. And that could be an application server as well. There could be an application server storing multiple apps, and it's just a common name application server. And that could be housing multiple apps, providing multiple different types of services out to the network and out to your users and computers and servers perhaps as well. And that's very important to make sure that all of your data is kept safe, that all of your data is backed up. It's elementary and almost every single organization needs some sort of a backup mechanism, backup process in place to make sure that all of your data is backed up. Now whether that be backing up your end user computers, your desktops and laptops. At least you need to make sure that your servers are being backed up. That data is being backed up to type to a hard drive to the Cloud, sent off site to another replication server in another location, whatever that is, it needs to be managed by some sort of a backup server. Now, the most common sorts of applications or backup processes or apps that you could use would be the big ones being vein, you've got CommVault, you've got Net Backup, you've got IBM's TSM as well, and there are some others out there as well. So backup, so about using these apps, configuring your backups. So if you do lose data, you have that confidence that your backups are there and that you can restore the data. Every computer on your network, every server on your network have updates that need to be installed from time to time. Of course, if you are familiar with IT a little bit and you've worked in IT and accompany, you will know that Microsoft release patches every second Tuesday of the month. I call it Patch Tuesday. Other companies, Apple, Linux as well, different versions there and even applications are releasing updates from time to time. Apps need to be updated, the operating system needs to be updated. These vendors don't just release patches for the sake of releasing patches, often they have identified some sort of a security vulnerability. There is something, there's a bug, there is something that needs to be fixed. There are perhaps updates, feature updates need to be deployed, and all of these can be managed in a patching serve up a server that is dedicated for patching. Common ones would be something like W SUS, which is used for patching out windows, computers and servers, SCCM. You've also got other ones such as jam for the Mac. And you've even got SolarWinds, Patch Manager and others. The ADA, which a third party patch management solutions for patching your fleet of computers and service management of phones. It'll be done somehow. So these are desk phones, perhaps even mobile phones, but we'll focus on desk phones, specifically VOIP, voice over IP. These phones need to be managed centrally somewhere. They're going to be connecting or at least communicating with sort of like some sort of a VOIP system, a PBX, something out to the outside world you're gonna be doing SIP trunks are going to be connecting to perhaps phone switching devices that you've got in your CMS cabinet, in your server cabinet as well. But it's all needs to be centrally managed within some system that can manage extensions, manage groups, all done through a phone server. If you do a lot of printing, even if you do a little bit of printing, you can have a print server also set up. Commonly if you're in a smaller organization or even in a medium organization, the print server services could actually be run on serve up. Some, some places actually have it running on the domain controller or their file server that just installed the printers onto there. But if you've got a lot of printers, perhaps you have multiple floors, you've got multiple buildings, multiple sites. It's sometimes a good idea to actually have a dedicated print server that is managing all of your printers, all of your printed queues, and all the relevant drivers for all of your printers, for both Mac and PC are the things that print servers are very common for as well, is now something like follow me printing or printing where you send a print. Again, C gets added to a cute within there. There's some specific print server software that is now tied to ID cards, to fobs, to sort of some sort of swiping device with a user now goes to a print up, swipes their pass onto the printer, and then the print will come out. It's more like a secure printing. And all of that is managed through print servers, FTP, and SMTP servers. If you have an external company who you need to send files to and from, you could house this within one of these FTP or SFTP servers. Of course, the differences between FTP or SFTP is SFTP is more secure and is encrypted, encrypted and things like that. So generally I would recommend SFTP, but they're very common to use still nowadays. You need to send a file to an external person. You store it into this SFTP. Perhaps the server is external facing, it has proper security. It's in what's called a DMZ or DMZ zone. And then you give credentials, set up an account for an external company that can then login and they have access to that file that you've just shared with them. And that's really the whole purpose of that server. So to ensure the health of all of your servers, you could set up some sort of a monitoring server. And this is a server where you actually install some software. You then scan your network, you add devices, you add servers into this monitoring software. And it essentially monitors the health of your equipment. The CPU, The ran, the hard-drive space. How is your sweet how your switches performing, how's your firewall performing intrusion detection sort of stuff. And there's a lot of apps that can do this really, really well. You've got things such as Ryan, you've got PRT, gee, you've got Nike OS is all of these other apps out there as well that can essentially control and monitor your service, for example. And then when things are triggered, when things are going wrong, when the CPU is too high, it sends alerts to the right people so that you know, when things go wrong and you can prevent things from going worse because you are alerted to something that may have happened on your network accordingly and then you can respond to it. If you're in a building that has some sort of building security, you have your doors that need passes. Perhaps you have cctv cameras, you have other sorts of security in your organization. I serve out or fleet of servers needs to manage this. Essentially you're building security. Again, passes cctv and other things like that about the security of your network. Now you can have firewalls that are software-based firewalls. You could have proxies that a software-based proxies. You can also have hardware firewalls where actually you go and buy yourself an actual hardware-based firewall, hardware based proxies. Or you can have software versions of those which are running on a server. So an example of this would be something like PF sense, which is a software-based firewall. You can also use it as a proxy or configure it with some sort of proxy services. And that is, that is sitting on a server. It's a Linux-based serve up, but it is acting as a firewall. And then you point your devices to go and filter the traffic in and out through your network, through a software-based firewall which is sitting on a server similar to that, you've also got load balancing service. Again, load balances can also be in a hardware form when you purchase load balancing service, or you can go software based load balancing service. Very good example of this is a website that get, that gets a lot of traffic. The last thing that you want to happen is you get tens of thousands, millions of hits on a website. And then that one website crashes because it cannot handle the traffic or you need traffic to be filtered between different locations. So what it does instead is it hits some sort of a load balancing server that then can spread the load across multiple locations based on a number of different requirements or prerequisites that you can figure out in that load balancing server. The next one is a terminal server or a remote desktop server. This is essentially like a jump box. So this is a place where people login to the server to then access something axis, perhaps another server. So for example, you may not want your staff to have direct access to a particular server. You might not want your IT staff don't have access to a particular server, but they can access services on another server through almost like a jump box or entry gate server, called a terminal server. And that could be for a specific purpose. So for example, you may know what your staff to access your domain controller directly. You know, you don't want Active Directory tools available to your IT staff by them logging into a domain controller. So you could set up a terminal server with the Active Directory tools installed onto there. And then of course that in turn talks to your domain controller. So your stuff access the terminal server to access the services from another server or some other application that could even be configured within a terminal server. Then we're talking about virtualization. Now we didn't talk about this too much. But of course you can have physical servers, you can have virtual service is equal service in the olden days, you would actually go and install physical servers, lots of them, and install one particular service on a physical server, you would install a file server on one physical server, mail server on another physical server, a DNS server on another physical server. Nowadays, a lot of this is all virtualized, so you get a physical server, you install some software onto that, you convert it into what's called a hypervisor. And then you can build multiple virtual machines within that hypervisor up. I would recommend going and checking out some of my videos when it badly. So if you do want to learn more, do check out that video right there. Well, we are talking about physical versus virtual service, so you can get a good understanding around that. But essentially, some physical servers you will keep could be converted into hypervisors. The most common ones being VMware as ES6, you've got Citrix, Xen server, you even got Microsoft Hyper-V. And essentially this is a host snail, a virtual host or physical host acting as a virtual hypervisor to allow you to install Virtual Machines so that you can then go and build your network, and then you go to server to essentially manage your fleet of servers. An example of this is VMware vCenter. This is a piece of application software that you install and set up on a server. And then you can go and manage your fleet of ESX. I harvest your VMware ESX host. So your, your fleet of hypervisors are managed by one central server, in this case called a vCenter Server. And the other vendors such as Microsoft and Citrix have similar things. Because the last thing that you wanna do is be logging into each individual hypervisor. We talked about that one before, one by one. So you have one central or a pool of central vCenter servers or virtualization server host servers to go and manage all the fleet in one centralized location. So that was the 20 we did a very, very brief snapshot on each of these, but hopefully you learned something.
9. Naming your Servers: We are going to be talking about server naming convention. How should you be structuring the name of a server in a business? Wouldn't it be wonderful if just from the server name, you could find out a whole bunch of information about that server. You may be able to know exactly where the center is located, what sort of server it is, and what sequence of numbers is just from the server name. So you don't have to necessarily go in, look up an asset register to find out another server because it's already built into the name of the server itself. Now before we even get started with the server name, you want to have make sure that it is a total. It's generally good practice to be a total length of 16 characters. Don't make the server name any longer than 16 characters. As a good practice, the server name at the very start should always contain the business name or at least an abbreviation, but ideally an abbreviation of the business name. And you may be saying, well look, I've only got one business and I've only got business. Abc fruits. I'm never going to have that name again, right? What if in the future that business gets acquired? What if in the future you've grown and you've acquired a new business, what if you don't have the business name in there and then you've got another business deal doing business with the same sort of name. Server, a one and that's it. And I've got another server, I wonder, do you think I know what am I supposed to do? Well, what if you have the name ABC server or a one and they had the FF server or one banded together. You now know that ABC was from business ABC and DEF was from business df, have the business name in there. So the business end could be a combination of two characters or three characters depending on how you want to abbreviate it. But again, keeping in mind that if you want to keep this 16 character limit, just form your structure around that. Perhaps in groups of three, halves, in groups of two, I preference generally groups of three. So if you've got a business called ABC fruits, I'll use the name ABC as the very start three characters of my server name. The next part of my server name is the location or the site. If you have multiple sites, perhaps in different suburbs, in different regions, in different areas, in different states and different cities in different countries, whatever it may be, incorporate that bit into the name. So let's say for example, I am ion in Australia, so I am in Melbourne. You've got Sydney, you've got brings them. So my abbreviation would be mgL for Melvin, SID for Sydney or be our AI for Brisbane. So I would have a name of a, B, C, and E L. So a straight away know from the name, it's Company ABC in Melbourne in MEL. So that's really the first bit. That is the information about the company, right? So if the company and the location of the particular office or whether particular server is residing. If a server resides in the Cloud, you may want to have it as AWS or I, as I said, IZ you for a zoo or you may want to be able to change that, but generally try to have it as a location of the actual server, company name and location, but then move into the distinctives of the server itself. What sort of server is it? Is it a production server? Is that a development server? Is that a false server? There's more than one file said, What do I do? The next three characters really is the environment of the server. What sort of TR, It's part of now generally, in most IT spaces, there is what's called a 40-odd model. So a server would generally fall into one of these four tiers, would fall under development stage at dP, dV for development could fall under a test stage. Txt protests before and the staging STG all fall under production PRD. So depending on where that server lives, you'll put it into a particular TEA, into a particular phase. So again, if it's a staging server, I'm going to say ABC, MEL, STG to straight away. I know in server that it's from company ABC. It's based in Melbourne and it's a staging server. All right. It's not a production server which you could potentially power the server down. I could change the cell without too much complications. If I see PRD in the name, I know straight away that it is a production server. And I need to be more cautious of what I'm going to be doing with that server. We then move into the function of the server. So we now know that it's in a particular tier, in a particular phase production, staging Dev or Test. Now, what does the server and do is an application server? Is that a domain controller? Is that a web server? Is that a database server, whatever it may be, put that into the name. So if it's a database server, you may wanna do dB. If it's a domain controller, dc for domain controller or AD for Active Directory. If it's a file server, you may want to be calling it FL or fs file server or FL file in or something like that. If it's a What's another example? An application server. So some applications, it could be a dumpy. You still have characters available and you'll be more specific. You can actually maybe give the name of the application, APP or F if it's application of office or ABP, EX application exchange, the name couldn't, the type would be male, ME NIL. So the function could be very varied depending on what the function of the server is. You don't have to be that specific on this specifically saying that it's just DB. You may want to be able to give it a bit more information. Again, keeping under 16 character limit, it could be calling it Db, Db EX because it's the exchange database server, something around those lines, but making sure and function of the server is listed in there. And then finally, the number or the sequence. So in many organizations you will have more than one of the same type of server. If you have a file server and you're calling it fs, or if you have three or four of these FS service, it may be a bit complicated. Just have fs and then what are you gonna hold? An excellent, so good practice to have fs 01 and the next all be fs 2, 0, 3, 0, 4, and onwards, the same deal, db 0, 1, 0, 2. So good practice. Always have a number at the end of your server name. Do not keep that blank. Have db, O1, O2, O3, O4 as your sequence. So there you have it. That is my general recommendations around a server naming convention. To summarize, we're really talking about firstly, the company name, the customer name, whatever it may be, which would be two or three characters, followed by the location or the site where it's actually physically located in a state, in a city, in a location and an office, whatever it may be. You then may want to spit into their potentially in the inner spaces. Or you could have the location if you have a very large office or if you have multilevels having, let's say if it's MEL, one made, maybe, maybe familiar one office on level 1 or MEL n Maybe it's the Melbourne office in the north side or in the south side or on the west side. You can actually abbreviate that a little bit more if you need to. That is followed by the environment. So whether if it's in production, in staging, development, or in the test phase followed by the function with its database server, a domain controller, file server, and application server. And then the sequence number of O1, O2 onwards.
10. What is a Switch: So what he just switched. In short, a switch is a piece of network hardware, so it's used in networking, in computing to connect computers together. So it's a physical piece of hardware with multiple ports to connect devices into those ports so that those two buses can talk to each other on a network. So generally, a switch is going to connect multiple devices in one single network you want single LAN or local area network. You're going to have other devices such as routers, connect different networks to get up. But in this case, the switch is just connecting devices on that same network together. So the connections can talk to each other and you can send information between one device and another devices that you connect into these switches. If you're at home, you've got a smallest switch. Most smallest switches at home would be either a full port, five port. A port switches, some you may get up to 16, but it's very rare in a home environment. Small office made him enlarge going to go into higher-end toggle switches where you have generally 16, 24 port, 48 ports switches, and then stacks of switches that can connect hundreds, if not thousands of different computers, printers, servers, and other networking equipment together to allow you to have communication throughout a network. The most common type of switch that we're gonna be talking about is what's called a Ethernet switch. This is i, standard network ports switch. Then the connectors, Apple II 45 cables, standard Cat 5, Cat 6 cables coming in from the devices running into the switches. There are different types of switches available in the corporate world, especially such as a fiber switch. We're going to be connecting five sorts of cables. But in this case, we're really focusing just on these ethernet based network switches. They can come in 10 meg, 100 meg gigabit, ten gigabit switches. You've probably seen 10 slash one hundred, ten hundred. That just means that it's capable of 10 one hundred, one hundred, ten hundred gigabit speeds. And then in the corporate world January and get 10 gigabit or even more depending on what that configuration may look like. The two main types of switches are unmanaged and managed switches and not managed switch is also called a dumb switch. What does that mean? So I unmanaged switch or demonstrates is a switch that really doesn't have any management capabilities. It's not as smart as a management switch. So you just literally have a switch with all of these ports. You plug-in your devices into this switch and it just gets you on the network. The traffic inside of that, of a robot switch node for the traffic should go. And it just does understand the traffic through. You can actually go in and configure the switch. It doesn't have a graphical user interface or permit or a command line. We can go in and configure the ports. You can configure the speed of ice pulls, you conjugate other management sorts of capabilities. I am management switch on the other hand, does allow you to have management of that switched. Generally, you'll find these in more of a corporate. Again, in the corporate world, we can log into the switch, can actually configure the spade and configured perhaps multiple V lands on a switch. You have management. You can see sort of traffic running through such as monitoring. You can configure clause which is quality of service as well on a switch. So unless you have a lot more management, sometimes you need that to be able to provide a different sort of service or segregate the network within a single switch. She touched on a little bit before, but modern day routes SAP have Imodium or router at home. They could also be a switched combined. So you might have a routers modem at LSE connect out to the Internet or Wi-Fi access or something like that. And I built in, switched to it. They could have a full port, Ethernet ports connected to it, which essentially is acting like a switch in a, all in one sort of device. You may also have heard the term hub. What is a hub? What is difference between a hub, a switch? So a hub in the olden days, you'd have to really find these as often anymore. They are still in use in some places. But I have essentially is a very, very not smart version of a switch, or we're going to treat them separately. But essentially a switch, as we've, as we've looked up, knows the destination and the source, IP addresses all the traffic that needs to be flowing through it. So it gets traffic coming in through one port and it knows where to send it to a different port. So it actually can segregate, can actually direct traffic in one particular, one particular path. I cannot do that. A hub just sort of sends the traffic everywhere and hopes for the bear. So how does it know where the traffic should be going? So as a result of that, a hub is going to send traffic everywhere. You're going to have what's called collisions of packets. So you, so you may have packets that dropped when he's going through a hub. And you also have performance issues because you're going to be essentially sending the traffic through every single port and then all the devices connected to a hub going to say, that's not for me, and it's going to block that traffic and early to one device that needs that trapezoid only separate. So it's not very smart and you look how it delivers traffic through a network. Cisco switches, the 10 gigabit switches. And you'll see that all of my blue type withdrawal my data cables running right into this particular switch, which then connects to a number of services to get me into the network, essentially network connectivity. You see that the switch run underneath it is housing and servicing all of my yellow cables, which are all of my phone. So this switch is essentially dedicated for fun, and this which is essentially dedicated full data. Now what you'll notice is on the switch, I've got some LED, so indicate a lights to let me know if there is activity on his particular network point. In this case, you see that this cable he is flushing. That means that if I trace this cable, this cable is going to go all the way into eye patch panel in the other Cabinet up the roof, over the roof. Particular port which correlates to this and plugged into a particular computer that he's currently on the network. So this is indicated there was knit with activity, knit with traffic through this particular port. So they haven't that is, I switch, I hope you found these helpful, hope you learned something new, and I hope you got the scheduled bit more clarification and definitions of what I switch.
11. What is a Router: In short, a router is a device that connects different networks together. So what do I mean by network? So these could be from one office to a different office. It could be from one subnet to a different subnets. Or subnet would be a range of IP. So for example, 192, 168 dot one dot 0 and everything in between 1 ons warranty site or one dot dot range. And then the 172 dot 16 dot one range. So two different IP ranges, which generally will not be able to communicate with each other. I forget to computers. And you plug them into a switch into a device that connects them together. One ys on 119 to 16, I got 11 is a 172, 16 dot one. They won't be able to connect to each other, will communicate to each other natively. So what you need to do is you need to stick a rash or in the middle of it. It creates some roles so that they can communicate now and it's usually nick those two networks together. So rather there's not necessarily connect you to the Internet. This is a very novel misconception with, I think a router is what gets you into the set that he's actually a modem. So motives, purpose is really to connect you out to the Internet. The rasa is to connect networks together. So sort of in a while, a modem is a router that connects you out to the global Internet, but not really in. We wanted to find the terms definitively. So rad is can be both wired and wireless. So depending on the setup, you might have a router at home. It could be in an office space in more of the corporate enterprise. Well, we have a physical router, you having multiple devices running into a route up to communicate two networks together. So for example, some switches were to switch over here and a switchover he with computers running into h and then they're on different networks. And then you've got connected with into a router, into an input, output into a, went into a land, pull, something like that to connect the two networks together. Then you've also got wireless routers. These are essentially the same sort of thing, but rather than physical connection, the physical network connection to buy, you know, like a Cat 5 or a Cat 6 cable. This is going over the Wi-Fi. So you've got a device connected to a Wi-Fi running into a wireless router. Routing table contains the information that Miranda nice to know where to send the traffic, where the incoming and outgoing, whereas the sender, the receiver, those sort of things. So it knows where to send that traffic. That information is kept in a routing table. And then in the corporate world, you can get a lot more fancy as well. So there are multiple ways to communicate between two networks. There's not just a standard one that harassing protocol. There are many different types of routing protocols depending on how you want traffic to flow from one network to another. All different pods difference sort of terminologies as well. Standard routing particles would be RIP, RIP, BIG, BIG up pay, Beijing. And there's a whole range of others as well, that sort of act. I guess the end goal is sort of the same, but the actual way that the traffic goes from point a to point B is different and varied so that you can go and if that is I wrapped up. So you've probably heard of switches, gateways, firewalls. But today we've talked about routers, we'll talk about those other terms in other videos. But they go, I simple rata is connecting two networks together.
12. What is a Firewall: In short, a firewall is a network device that controls the security of a network. It monitors and controls the incoming and outgoing traffic flowing viral network. So computers that communicate by each other. Computers I connect out to the Internet. The Internet connecting back into a computer into a network generally should flow through a firewall of some sort. So a firewall essentially analyzes the traffic, analyzes the packets, and can stop or control the traffic that is flowing through it. So for example, I've got the eye a particular network in the 19 to 16 site dot one range. And then I'll put another network on a different range. And I only want certain traffic or certain computers to be able to communicate to computers. On the other end, I can actually allow or block certain IP addresses from actually communicating to other devices on the network. You can also control ports. So for example, if you don't want to FTP to be open or you don't want to be able to use HTTP, which is your website's over port 80. You can block port 80 on the firewall so it doesn't allow port 80 to float from 1 to another. And that's also true from connecting up into the Internet and back into your internal network. So generally, you're going to have a firewall the most part it's the most common use of a final will be to control the traffic flowing in and out of a network from the internet. Very similar. You've got a whole heap of devices on the Internet that are always trying to get in to internal networks. You know, you've got people like hackers, people who want to get information, malicious, malicious attacks. And they are generally going to be stopped or prevented verifiable. So you can allow and disallow certain traffic from flowing through this file into a network. Firewalls can be physical, like heavy hardware based or can be software-based. A physical hardware is a physical device like a, like a similar to like a modem or wrapped up where you have network connect is running into it. And then you can have different sections in that firewall to control the traffic. And the traffic is actually physically throwing flowing through that firewall. You've got big vendors such as Cisco, they've got CSCA, ISAs, your Juniper as well. There's other vendors such as Fortinet, Palo Alto. There's a whole range of a pretty high-end brands of firewalls that lets you control the traffic. Other examples of physical firewalls could be your home router, your home modem, but I could also have firewall capabilities. So nowadays, most home end device that lets you connect out to the Internet have built-in firewall functionality to be able to allow or disallow traffic, so you can actually get filed in a lower-end home devices. Also, software-based firewalls could be something like your standard Windows Firewall that's built into your computer, built-in to a Window Server. You then got other software follows such as PF sense, which is a free open-source firewall, we start to do very similar functionality to hardware-based, but rather than it being hardware, it has to flow through the software-based firewall. So you're essentially point or your traffic to flow through the software, software firewall rather than flowing through your network firewall. So there you go. That is a very high-level overview of what a firewall is, a water firewood.
13. SAN vs NAS Overview: I guess it was called file-based. So it is completely dependent on SMB and NFS protocols acting as a file server. While I SAN is what's called block-based block and file a two different sorts of technologies. And generally when you're hearing the term SAN, we are talking about block base. When you hear the term now as you're talking about file-based, it stores any data that you particularly want to store in a centrally managed location. What you will do with the NES, have all of these disks that you put into a physical illness. And then you combine these disks together into what's called raid groups. You create storage pools, you create volumes that are then presented to a network. Volumes you can create. For example, SMB shares, NFS shares, which essentially at the combinations of those disks that are the rights and storage pool that you've created, that are made up of physical hard drives that are inside the NASW. So in the olden days, you will just have a file server that you'd have a physical disk connected inside of a server in a PC, and that can become a false server and that's where you store all of your data. You, what you do now is you have what's called a Nas and that replaces your traditional file server. And now you are managing all of your files and everything, all within a hardware based storage network, as said, is essentially a block of this is very similar to this, to the NAS. From a hardware perspective, you've still got a physical piece of hardware that contains multiple disks created into different right groups, into different pools, storage pools, and then a created into what's called a LAN. So unlike the Naz, we have a volume or a SMB or an NFS share. On the same side, you've got the group of disks that are created in what's called a LAN or a logical unit number. This is a group of disks that are then presented to a particular service, generally a nasa we use, as I said, for fall service. I said will be used for services such as a virtualization environment, perhaps VMware, etc. In short, a sane is presented to a server or a service as if it's a disc that is locally attached to the computer. The operating system point of view, you will see it as if it's physics connected into that server or that computer. The two most common protocols that are used by Sainz are ice, Ghazi, and fiber channel. So you can provide these lessons to a server. Let's talk about VMware ESX I, for example, I put a VMware ESX server, which is used for creating virtual machines. And I can see I can dump those vertices or store those virtual machines on a LAN which is presented to the ESX host over ice Ghazi are over 50 channel from an ice Qazi perspective, I've gotten the two wins and my sand, it has my lunch. And then I've got my VMware side, create what's called a path between those two using ice Qazi initiators, it's using a WWL or an ICU. And these are the sort of the unique identifies. The ice Qazi initiated interprets the connections between the two physical devices. And then I just provide that LAN from my sand to my host over IS Gazi. There is a number of Priam backend configuration that needs to be done on the sand and on the VMware has to allow the communication to happen between the two. But once that he's established, presented over ice Qazi through the ice, Qazi initiator. Ones that is presented to the VM or a side, I think in create what's called a datastore from that line, which then are used as just a bunch of disks to be able to then go and create my VMs. Ice Qazi generally can be transferred over the Ethernet protocol. So you can use existing Ethernet switches. So you've already got your network switches such as your Cisco, HP, those to the vendors which do already Network ethernet switches over RJ-45 network cables. And you can pass the ICRC protocol over this IP, internet protocol packets. So you don't need any other fancy equipment. You just really need your network switches to be able to pass your IS Gazi traffic over. The alternative to IS Gazi generally is fiber channel. This is more of a dedicated fiber connect up between your second and your server or your ESX hosts. In this example, you can connect a sand directly to an ES6 I host over 50 channel. The fiber channel COD will be required on the back of a SAN. And on the the x-axis, the ASX 100 hosts. And then you'll have a fiber channel cable connecting the two together. And then you can establish the connection that way. Commonly in a larger organization, you're going to have fiber Channel switches where you are running multiple fiber channel cables between the sand, between the storage processes on the back of a sand into these fiber Channel switches. And then from multiple HBI kinds of fibre Channel cards on the back of your service, your ESX hosts, for example, into these fiber Channel switches. And then he create what's called zones between these channels to let the, I guess the five atrophic no way to go and what traffic from one device to another. You can also set up multiple levels of redundancy this way over the fiber Channel switches using these different zones to let the traffic note which way the Trevi should be flowing. So really in short, there is no answer to which one is better because I do provide different services. So you've really got to ask yourself, what is the purpose? What do I need to do in my organization? Or even if you're doing this for a lab perspective at home, is what do I want to achieve if I just want a place to dump a whole bunch of files that don't my movies, to dump documents, to dump my data, et cetera. You may want to look at the Nasdaq base for the fall based option if you want to use it for say, building virtual servers, to be able to just provide a big dump of disks, essentially raw data, to a server such as a virtual hypervisor server. You then want to go down the same route. So really DIA, the differences you gotta fall based, which is known as block-based, which is said. And they really provide different services depending on what you're quiet.
14. SAN Hardware: In short, I storage device such as this is going to be used in an enterprise, in a business device to store a whole bunch of data, essentially unit like this can be expanded significantly. You can add multiple levels of additional disks, disk arise. This will easily go into the petabytes you that concern as long as you have the money and the resources and the spice in a rack to be able to continually expand, the storage is going to be used for our VMware virtualization environments. So essentially I've got all of my service set up, need to share some storage. I'm going to be creating different storage pools. I'm going to be creating what's called lens. Essentially a blocks of discs which are and then allocate into VMware, set them up as I Datastore, and then build my VMs and allocate those VMs to a particular datastore for storage. The good thing about having something like this as opposed to having the storage on the server, is that I've got one centralized location for all of my storage of a multiple levels of redundancy, almost storage as well. And I'm not limited to the storage on a server, for example. So this is a SAN, it can also be configured as an S. So this is essentially a storage unit. For your business. You generally wouldn't have something like this in a home environment generally for a small, medium, or large organization, you'd set up something like this that would be recognized as you can see, it's erect space unit. So on the side of these you're going to put your Rails and then actually put it into a cabinet. So this one is a Dell EMC unity. And as I said, it can be configured as a SAN or a Naz. The main difference being that as sand is a storage area network which he's blocked base or you use it for something like VMware or some visualization technology. Or Naz can be configured for SMB shares, NFS shares, which essentially acts like a file server. And you'll see here, I've got this essentially just a panel that's on the front of the unit itself. There's a little keyhole HE, where you can open and close or locket, I should say, so that you kinda actually type this panel off. So this is just a fancy panel to make the actual device look enticing, make it look nice. But you'll see that on either end, you've got these little latches. And if you pull, you actually get the panel to come off. And you'll see the inside of the unit while the front of the unit anyway without the panel, you'll see that he, I've just got a number of hard drives connected. So these are the hard drives that are on this particular SAN or NAS device. You'll see that they are SAS drives. These particular ones are 1.8 terabytes and they had 10 K space. This is essentially the state of the discs themselves. And they easily just slaughter ball right here. And you see that all of these slots here are empty. So to essentially insert and remove a disk, you just click on the little latch, just the bottom here. You'll see a little bit, a little lunch comes up and you slide the hard-drive run out. So this is just a standard 2.5 inch disk drive. You can get storage which has the larger 3.5 inch. But these 2.5, they Dell EMC drives and go to hold information there about the drugs themselves. While I'm pointing at terabytes, you see that the hard-drive is just within a normal enclosure. So you've got the connector for the hard-drive, right? He into the connector into the adept to heat, which then would slot in. So this is just a standard enclosure that is required. And then to put it in, you literally just push it in and then put the latch down like so. So you see that all of these are empty. So when I do require some additional hard drive space, I literally just purchase these new hard drives. You can cross the vendors So you can buy say, a Seagate or a Western Digital hard drive. I'm an admin. Generally it's a good recommendation to try to keep the vendors the same, keep the models assigned as much as possible, even though they will work if they are different models and try to keep the space to the same as well. A good example is what I can do is when I went, I power this unit on, I can configure the, the, the, you know, the disks to be in groups of raided disks in different pools. So I can say have these five disks, right? He set up in a right Five pull. If I then add some more disks and I want to add them to an existing pool that may exist. I may not be able to if they're different sizes, so you always want to try to keep it the same size if you expand a particular pool. Otherwise, you can buy different size disks if you want to create some new pools of new spot. Way, what you do is you literally would just take this out like so. And then you swap a new hard drive in with the enclosure itself. And this is literally just a cava, just to cover this empty call doesn't actually have anything on it as you can save. And obviously we'll leave this on here because there is no hard-drive on the side of the unit. You've got your little tag, which if you pull this out, has some information about your actual sand as devise your storage device, including the serial number that you can look up for warranty reasons. Today we've got the rails of the actual SAN or NAS device. This is going to be attached to the side of my unit right here. So you'll see that on the back. Essentially I just slot this part out, put that aside, and then I would just screw that in, sort actually put it onto the side of the unit, screw it in. And then on my rock itself for my actual cabinets, I would attach this to the actual side of my front and to the back of my cabinet. So this would slot in, all right. And then that is fastly in place. And then I can literally just grab my actual device with this side attached. Obviously you're screwed in and it should be able to just slide into place, series the back of the storage device. All right. Now, generally most stores devices are set up to have dual storage processes. They called SP storage processes, which essentially is what contains the CPU, the RAM, the peripheral devices, et cetera. And there's generally two of them for high availability and redundancy. The reason you do that, He's obviously if you only have one which contains one power, one network point, et cetera, et cetera. If there's a problem with that storage process up, then your entire sand or NAS will become unavailable. There are two here for the purpose of redundancy, high availability, and also an element of load balancing so that they, you know, they can take equal amounts of load rather than putting all the load on one particular storage process up. So you say that H story processor has a power, right? You obviously want to power the unit. And if this one goes down, then this one is still powered and you're still good to go. So the general way that you would set the subsidies, You'd obviously be running one power into one rail, one, the other power into a different Ryle, into different power sources for high availability. Because again, there's no point in having the power running from two different storage processes into the one, power rail, into the one paid to you. And then that PDA, you guys down, that power L goes down and then you lose power. So you've got a couple of connectors here as well, which are used to connect multiple units together. So once this particular unit is full of disks, and you want to buy some additional disks you by what's called a disk array, which essentially a separate disk array, which is going to be connected via these connectors, right? He daisy chain them together essentially to form a larger pool of disks which you can then use to splice up and slice your storage as needed. Got a couple of fibers Connect, does heat senate LC connectors to actually connecting two into a fiber switch or directly into a server that has fiber connectivity to going to be using fiber cables for those. And then we've also got our Ethernet connect, this right here. This is 10 gigabit ethernet, going to be running my Ethernet ports and cables in today's and then likewise into subsequent switches or directly into a survey for only got one server. But generally you're going to run these into different switches. And then you would say that there were two per storage process up again, that he's all set up for redundancy, for load balancing. And obviously good practice is to have those running into different switches. Otherwise it defeats the purpose of having load balancing and high availability. If your switch goes down, then everything will guard down. And a couple of other poets, you've got one gigabit ports as well on each storage processor. And then I management port as well. We can actually use to connect into the device to perform management and do everything that you need to do from a console perspective. So the actual storage process essentially starts from here to here. And from here to here, each having their own subsequent power can easily just change the power unit. So if this particular power became unavailable, you can easily just pull this one out as well, slaughtered out completely, buy a brand new one. And you see that there's actually module slot CIA. So on each different sets I guess here of your, of your storage device and you can add additional causes, essentially additional functionality to each of the units. So if you need to buy some another 50 cod, you need to buy some more network points, whatever it may be, purchased them, sort them straight in here. You're good to go. And again, these are just really just covers to just protect the insides rather than just having an empty hole. That's normal. So unit power on. Super nice lady, things are all working as expected. And then each corresponding, this has got its own subsequent LED. Don't know what he produced is working well, whether it needs replacement. You see that there's actually lots to the right of h disk, which will be turning a different column, generally a red or an orange to let you know that there's something gone wrong and requires a replacement. So we're here now inside about combs room, does our Comms cabinets. We are going to be racking the unit. And you'll see that I've just got a number of slots CH, so essentially I'm going to attach the rails on the left and on the right. And then once that ease in on the front and on the back of the unit, I can then slide my device seen as normal and then are good to go OK. And then connected, I can connect it into my particular, to my particular switches, into my particular powers on my left hand and right. And then get that on the network and go ahead and configure it and then use it. So here's an example of a device that is racked. So you've got the cabinet right here. You've got the rail that's hooked up into the cabinet. And then you've got the actual system itself, which is connected to the rail. We saw the top, this is the actual unit itself. And then the rail runs all along the side here, and it's actually mounted into the actual side of the system and then onto the front and now to the back. So the most units will either be to IU or one IU or more depending on how big it is. This particular unit that the example that we're looking at here, this is a two IU units to sign up to rock unit spaces. I wanna, you would essentially be half of that space. And you see that right here. It's actually going to be clicked into one spot, but is capable of taking up to the two i u. So obviously whenever you're racking one of the systems, you want to make sure that you've got enough capacity, enough storage space to be able to accommodate other the one I you will have to IU or largest space.
15. Backups Configs + Types: So every single business nice to have an adequate system in place to manage backups of your data in worst-case scenarios, if you don't have proper backups in place and you lose all your systems and you cannot recover your systems, you could potentially going out of business. It's very important to have backups that accurate back-ups it had done regularly. And backups that are not only done on site, but also sent off site in case you're on-site, infrastructure is destroyed or is unavailable due to a disaster. Backups can be of the entire system, but can also be granular as well, which essentially MSI or Beck, the file level, the folder level, files in a system. Also, depending on the technology that you use, you could have backup agents running on individual systems which essentially communicate to a backup server. And then that is controlling your entire backup fleet. It manages your your scheduling, what groups, what servers, what systems you want to backup when, how often? If they wanted to incrementally, if I want to be fooled, really the type of data as well. If you've got, for example, a SQL or SQL Server and Exchange Server, SharePoint Server. They may have independent, different types of agents required to be our backup this data and then Locke was to be able to restore this data. Also, other systems can integrate directly into your hypervisor. So we mentioned VMware, Citrix, and Microsoft hot integrate directly into your, um, your virtualization environment, interrogate all of your VMs and do a full fall based snapshot based backup directly on your hypervisor, communicating directly into a backup system, daily backups generally will be called incremental backups. Essentially what incremental backups up is, a full backup will take place. The first very first backup will be a full backup backstopping entire system. And then a daily incremental we'll be putting place potentially backs up with changes that had been made since the last, full or last incremental backup. So if you have daily incremental backups, if I have an incremental backup on the Wednesday and I also had on Tuesday or Wednesday, we'll only backup the changes from the Tuesday, the day before, which backed up the changes from the incremental on the Monday, which may have backed up all the changes since the first full, which happened perhaps on a Saturday or on a Sunday. So it daily incremental then move into weekly full backups. The general good practices to have a weekly full backup, at least one every week we do a full clean slate backup of all of your systems. So this can include all of your servers and again, your workstations if you do have that system in place. So you've got daily incremental every single day of the week, except for one which you differentiate, it would be a full backup that could happen Friday and Saturday or Sunday. Whatever day you choose has to be a day that has had the most changes within the hallway. Can you determine this is the last day per week essentially, but I want to do a backup and that's going to be a full backup, which is a fourth system state of 4-bit snapshot on retry server for example, once a week from your weeklies, you then also can include monthly and annual backups as well. A monthly backup, essentially BI full backup as well. As well as your annual backup could be a full backup. Some companies do it differently, but you could actually have, you know, you've got a full full sets of weekly backups or five sets of weekly backups in a month. One of those, perhaps the last one at the end of the month or last weekly fool could be turned into your monthly full or you could set up a new job to a completely new backup which is a monthly full Same deal with your annual. Annual could be the last backup of the month. The last full backup could be the symbol, the last monthly backup in December, which is could be the last week we fall in December becomes your annual and then I think goes off site and is retained for an X-Men time. So if you've got systems, if you've got workstations, you put your end user computers or desktops or laptops. They could contain business data that requires backups. So there's two really, two big things that you can either do. One, you allow your staff to run business data on their own computers, but then you have to have sort of a mechanism where that data is then backed up to a server, which is backed up by a backup system, and then it sends to a backup repository of some sort. So you can actually have Tool software installed on every page. Computer automatically copies all the data from the computer to a server, for example, or a storage device. You alternate, which is generally the way that most businesses will door it is a user will have access to a number of shares. They'll have access to. A file server, will have access to at age drug which is like a phone dr, which is their own personal space. And the recommendation would be that staff do not save business data locally on your computer. Rather, they're saving it in these shared drives in a server drives. Which in turn and have software for backing up in the background. And that way it's old, manage that way. So you don't actually putting an extra piece of software on every computer to manage backups of all those workstations. Regardless of how often you do the backups, you need to determine where those backups opponents as gets sent to. So you're only going to have on-site and off-site or a combination of the two in terms of where the repository of those backups are currently living. If they're on site, you've got a number of servers, number of systems, and they're going to be backed up to some form of media. And that could be a combination of another server with a lot of disk space. It could be a storage device such as a sand renounce. It could be even external hard drives. If you want to go down that method. It could be taped libraries. You can have tapes such as Saltillo tapes, which are then routinely shuffled around. And they are then save on-site in premise within your organization or within your data center. If you lose that entire cons are many types severing or their data centers and available, then you've lost not only your production service, but you've also lost the backup systems which are also residing in the same location. So what you do is additional to on-site backups. You also have off-site backups. Backups that not only reside on site, but are also copied or moved to off-site locations. So if we use these terms again, these technologies, if you're vacuuming up to another server, the server could have speak at an alternate location. If you're backing up to a sand or Inez, you could be backing up to that. And then he turned that could be replicated to a ultimate location, this, this server and ask for them, you've backed up to another sermon as somewhere else. You could also then back up to tapes. So I mentioned our TO tape. So you've got LTI 5 else there six LTE or seven types of types which have a certain amount of terabytes later on each type. You then have the backups copied onto these types. These types go through like a weekly, daily or a weekly cycle with a set of sight to a third party company. And then you add the confidence that these data is offsite. The same deal. A lot of smaller businesses will have a external hard drive plugged into it to their server. Data gets backed up to that and it's somebody's, somebody's responsibility. They take that hard-drive sites and Mitchell of the data is safe offsite if something on-premise happens. The other option is, of course, save it onto the Cloud. There are a lot of Cloud-based backup solutions out there. We can have all of your backups running off to the cloud and they essentially then a off-site they siphon offsite location. If they are on the Cloud, you need to consider what your retention requirements are. How long are you going to keep data? So this is really going to determine, be determined by the type of data that you'd have got. So certain images or certain videos may not be required to be retained for seven years. But for financial data, data that deals with human resources or admin, things that have been warrant requirement or legal requirement for you as a business to retain may require a higher retention period of 17, 10 years, or even infinite depending on the requirement. So really the important thing is, yes, not only to have backups and replication in place, but also have a plan in place so that you know how long you should be retaining this data for legal requirements, auditing requirements, financial data is fuel tank for certain amounts of time, tax purposes. So really determined your retention periods depending on the data that you've got and how it you need to be keeping this data really quick overview of a full incremental and differential backup and the differences between I've got a survey that has never been backed up before. The very first backup is always going to be a full backup. And this could be done on a Monday, for example. Monday backup first full backup contains a copy of everything that I've determined that I want to backup files, folders for the entire VM, whatever it might be, the entire server. First backup will always be full. And x backup, which perhaps I've got scheduled for the Tuesday, is going to be an incremental incremental backup. Is all the changes made since the last full backup on the server to server has had new files added on the Tuesday. So the full backup will be checked against the incremental backup and any files that have been added, any positive been edited, will then be backed up. It will not touch everything else because this first full backup is already got copies and he's covering that components. The Wednesday backup will also be an incremental backup, which is only going to reference the changes from the last incremental backup, which references the changes or the first backup done in that first full backup. Similar that pattern continues into Thursday. It will reference the last incremental, which in our case is the Wednesday, which references the last incremental, which is the Tuesday which references the first full Monday. Now the full backup on that Monday, my next backup is now going to be an incremental backup. Again, it's only going to do the changes from this full this foal is now irrelevant to this backup. So this backup will not reference this full or any of the incrementals in that last week because this new full has essentially started the counter again, right? So this next backup and every subsequent until the next full will be incrementals referencing the previous incremental referencing the last full backup. A differential is slightly different. I'll go my first full backup on that Monday, perform a differential backup. This is now going to be similar to an incremental in a sense that the differential only backup the changes made since the last full because the full already has got all these other faults covered. My next differential will now only back at the changes made since the last full. Remember the incremental references and loss incremental, the differential references, the last full. So in reality, the changes made from the differential will only reference the changes made from the full. My next differential will not reference the changes made from the last differential on the Wednesday, all the Tuesday. Rather. We'll reference the changes may from my phone, full backup is the first initial backup and any subsequent full backups or to schedule the incremental always reference the last full and every further incremental reference for last incremental until the first full and that gets reset when the next full can takes place. The differential references, the last full backup and early that backs up the changes since the last full backup.
16. Cabling an Office: We're going to look at how does a computer on a disk. So you may be working in a building. You've got computers set up around the office space and they're connected into the network and they will run into something like what he's behind me, a comms cabinet, a civic have enough, how is it all connected together? Where do all the pods fit in? So let's go through a lot of that right now. Here we go. Just a standard computer. Nothing special. But of course, the side of my computer has a network point. The computer itself could also be plugged into a dock, which has a network point which runs into that. And then that is going to run out into a particular cabinet. So here we go to sustain IT. Network cable. This is what's called a Ethernet cable. This is an RJ45 connector, and this is a Cat 6 cable. They also will come Cat 5, Cat 5, 8 and various combinations. So this essentially is the cable and Ethernet cable that's going to run into your computer, into the side of your computer or into the side of your phone. And then that will connect into a particular port that is situated, need the computer itself. So here's an example of those wall points. This is on a actual wall itself. So you'll see that somewhere underneath, some can be on the top. And then you've got a couple of Ethan and points with an actual reference number, whi, which will match up to the reference number on the patch panel. But essentially you can see that out of the back of the computer, we've got a blue cable running into a particular port with a particular number for reference. And my phone run into a different port next to that one. Ah, references also that I can track essentially where that's going. So that isn't going to run up the wall, which will say now. And that runs into Out Server, into our Racket cabinet itself. And that is being fed all into this one symbol, chain of cables that are running up into the roof. And then if I lifted up that roof panel at the top, you'll see that the cables all run all the way into our server and comms cabinet, which then fed into a patch panel, into a switch. If your computer doesn't require a Ethernet cable running into it, you may be wondering how does that work? Well, this is a wireless access point. It's called a wet wireless access point. This is a Fortinet wireless access points. And essentially this on its own, we'll have a Ethernet cable running into it. So one of those same blue cable that you saw that is connected into a computer directly, is running into the bottom, into the back of one of these devices. And then likewise going up to the roof into a patch panel that is in my mom's cabinet. So regardless of whether you are physically plugged in via cable or using the Wi-Fi, there is still some physical connection and needs to be running into your CMS cabinet. And then they're all essentially coming into a centralized location or multiple centralized locations across your building. So in this case, we've got a whole bunch of purple cat 6 cables. These are ethernet cables that are running for each individual port on each individual desk running down into this particular cabinet. Then each of those will then correlate to a particular patch panel. So these are the back of the patch panels. You'll see that each cable that comes down from the roof runs into an actual port in the back of a patch panel. This cable is then spliced open to reveal each of the sets of cables that are within each Cat 6 or Cat 5 cable. And they are then connected into the back of this touch panel. So you'll see in this case there is a number of different cables running into a range of different touch panels. These patch panels could be configured to have just a voice. For example, for your VOIP phones, fields, telephony, all that could be running from your computers, from the actual fine ports and from the computer ports themselves, and could be split up separately. So for example, this one could be just for computers based on, could be just the phones. This one could be four for servers or network switches, et cetera. So depending on the size of the organization, some cables may be going to different areas that are going to be spliced differently. And then obviously once they go off into the roof, they're going to go into the different sections across the building and across the different services. So here we've got the front of the patch panel. So you will see that from, but from behind we obviously had the purple cables. You can sort of see the PebblePad. It was just through the back there. And they are now running into the front. So obviously we've got the purple cables on the back that had been spliced cyclin. And now I've got the front and Ethernet ports essentially is the other end of the Ethernet port available here where I can now plug in further cables. And you will see that each single one of these patch, essentially the patch panel, is labeled. And at the desk themselves where I've got the physical ports on my fighter for my data, I've got an actual ID number and actual number that lets me know that this port is running into this particular port on my desk. So it easily, it makes it easy to track exactly where the cables are going. If this was not labeled, then I would have no clear visibility of where this port physically goes. Unless I have some sort of a network diagram or a network matrix or map that sort of dictates where that data is actually gone with it. Cable actually going. I compute out or a fine that is plugged into a port, comes in through that back purple port, and then we'll run into a port on the front here. And that is then dictated by the cables which are running into these, which are essentially another cat 50, Cat 6 cable which will run into a switch. So here essentially what we're looking at, we've got an empty Ethernet port that at the moment is physically connected into this location right here. So on the other end of this, if this is not connected into a switch, then I can plug in a computer into this particular port wherever that may be in my building. And it's not going to really do anything because if you've traced that came from 1 to another, is going to come to here. And because this port does not go anywhere, does not go into a switch, not going to get a network, the network IP address. So what you do is you need to get a cable, run it into there, and then write it into a subsequent switch. In the case of what we've got here, because we've got two cabinets that are essentially right next to each other. So this particular cabinet is going to house my patch panels and the cabinet next to it is going to house my switches, which is essentially where all of these ports are going to be running into, into a switch. And then the switch will connect to a number of back-end services, which will provide a relevant IP address and connectivity into the network for a device that is connected into either of these ports. So on the other end is the cabinet right next door. You'll see that all the cables are now running into these switches. These are cisco switches, ten gigabit switches. And you see that all of my blue cable to draw my data cables are running right into this particular switch, which then connects to a number of services to get me into the network, essentially network connectivity. We say that the switch right underneath it is housing and servicing all of my yellow cables, which are all of my phone. So this switch is essentially dedicated for Foreign, and this switch is essentially dedicated for data. Now what you'll notice is on the switch, I've got some LED indicator lights to let me know if there is activity on this particular network point. In this case, you see that this cable he is flushing. That means that if I trace this cable, this cable is going to go all the way into a patch panel in the other Cabinet up the roof, over the roof to the particular port, which correlates to this and plugged into a particular computer that is currently on the network. So this is indicating there is net with activity network traffic through this particular port. So once you compute it is connected into the network and into running into all of our infrastructure. He is running into a patch panel, it's rolling and running into a switch. It's then going to be connected to some services in the backend, which is going to be giving it an IP address and connected into the network. Now we're not gonna go into detail of the functionality or the how that actually worked. But in short, it's going to go and query what's called a DHCP server, which is essentially a server that is spitting out IP addresses out on the network. You'll computers in a site. I need an IP address, is going to say, where is there a DHCP server, the DHCP server civil site. Here I am. It'll give it an IP address. That IP address will be given to that computer, to the, now that computer can access the network, it will be able to go through a different number of different ways to get to the network it could be traversing by a firewall device switches via route is over different IP ranges, a different subnets or ever number different solar technologies, security procedures to make sure that a computer is valid and is acceptable into the network. It will go by services like DNS to be able to get authentication to a domain controller, which will give it an authentication into a network or a username and password. But that in short, is what is going to be happening on the backend once you physically plug a computer into the network to be able to get access onto the internet, onto the network.
17. Common Cyber Attacks: Going to be looking at the most common types of cyber attacks. Intended purpose is to damage operations, to have a financial impact, to steal information, whatever it may be. We're going to look through these top 10. Now cyber criminals and cyber attacks are getting smarter and smarter all the time. People are now working more and more from home, working more remotely than ever before. So the attacks are a lot more common than they were before as well. The first one that we're going to talk about is malware. Malware is short for malicious software, and it's really just some sort of software that is intended to cause damage to a computer system. So things such as viruses, worms, trojans are all type of malware. Often malware can reproduce and spread across the network. Malware attacks can cause a system to stop operating. Data can be lost. You can actually get access to a system as well. If that malware is smart enough to be able to intercept, say, passwords and things like that so that you can actually have a remote access into a system via a known vulnerability as well. Number two is fishing with a pH, fishing, as the name suggests, think about it as phishing, a line a set out into the network, into a individual uses email wherever it may be. And then somebody grabs that fishing line and it drags them in, intended to deceive that person into perhaps clicking on a link or following certain instructions. But actually that e-mail is malicious and he's not genuine. If you look closely an e-mail, we'll have suspicious signs to it. Often emails that have phishing emails will have a sense of urgency to them, urging you to do something to take a particular action and often clicking on a link or clicking on an attachment in a phishing email, my redirect you to a website that is not genuine. It might look like the real deal or it could introduce something malicious into your computer. Often, malware can come into a system through a phishing email, sometimes efficient Emma could also be targeted. It could be customized to you specifically to your name, and could be even looking like it is legitimate coming from somebody say within an organisation, I common technique is to have an email sent to you via say, a person in a senior position in an organization, perhaps a CEO or somebody in the finance team asking you to do something. And often because you see it coming from somebody that is important, you're more likely to go and click on that and action what it's stating. A very common type of attack is what's called a denial of service or a DOS, or a DOS, commonly against a website or a network or Sunday that is facing the Internet in some way. So targeting that website or the backend database with a lot more requests than what it's usually used to could bring that website down. Most sophisticated way is a DDoS, a DDos or a distributed denial of service where it's not happening from one single source but from multiple sources all at the same time. Potentially a pool of computers, multiple Pings to one website, multiple Pings to a group of websites or databases with the hope of overloading the system, overloading the bandwidth to be able to then bring that system down. Another common one that is really grown in popularity over the last number of years is something that's called ransomware. It requires a person to pay a ransom to get that piece of malware, that piece of ransomware taken off a system, commonly ransom way we'll get onto a computer system in a number of different ways. We sort of touched on fishing before, for example, could potentially encrypt and number of files on that computer. A warning message could be displayed on that computer screen telling that person that they files have been encrypted, they files have been lost. And if you want to decrypt these falls or recover these files to go and pay the ransom. That could also be targeted by saying, you know, we've detected something suspicious on your computer. Pay this ransom to be able to remove it, or we notice your web traffic, we're going to report that unless you pass the ransom. The next one is I password attack. This is very, very common. It happens all the time. This could be against a website, it could be against an individual, it could be against a group of individuals. But essentially the goal is to try to guess and crack that person or that websites password to gain access. They want to get access into a network, into a website, into a uses Facebook, YouTube account, whatever it may be, by guessing that password, there could be elements of even social engineering to try to trick the user into providing information. Secret question and says things like that to be able to gain access by cracking that password. Now the two most common techniques, brute force and dictionary attacks. Brute force, as the name suggests, is we're just going to try to brute force our way to guess that password is. It could just be trying a whole range of different words and combinations of words and letters and special characters try to get access to that particular system or that particular uses account. It may try things such as that uses name, the address, the date of birth, hobbies, job titles, workplaces, a number of different things to try to brute force its way. In. The other type is dictionary attack, and that's the name suggests. It could start with the most commonly used passwords. Passwords such as password, passwords, such as admin passwords such as admin 123. There's generally a common ten, common 100 common thousand types of passwords and combinations of those passwords through a dictionary of sorts to try to guess what that password may be. The next one is a man in the middle attack. And as the name sort of suggests, it's when something is placed in between the source and the destination. So for example, you are a user trying to access a particular website. You could be in a hotel connected to a Wi-Fi network that is managed by that hotel. Hotel Wi-Fi is intercepted by this man in the middle, by an actual person or a hacker roles as different source that is monitoring the traffic that is connected to it. You then access the website through this man in the middle, through these Wi-Fi network and all of that traffic can be viewed and intercepted. Another common example is we talked about this briefly in the fishing type of attack, a phishing email is received that links you to a fake website, perhaps a banking website that looks legitimate and looks like your bank's website, you then login. But that is actually a man in the middle attack because that website is not actually your end website. It is a fake website. You then login, it then registers your credentials and the nose credentials can then be used by the attacker to go and actually login to the actual correct website. Very interesting one is one called crypto jacking. You're all probably familiar with cryptocurrency, digital currency, Bitcoin and other sorts of theory, um, and other sorts of currency coins that are out there. Digital currency coins that are out there that uses malware to install software onto somebody's computer to then go and act like a minor. So hackers can use this type of malware to crypt her jacket competed to do the work for them. I very common way that hackers gain access to websites and actually stealing information through databases is what's called SQL injection or SQL injection. Essentially what this is is somebody that is accessing a website that has a back-end database to it. And a lot of websites do and executing particular commands in a search field, in a login field that is querying a backend database is insecure if the website or the database has not been set up properly and there are vulnerabilities and holes in the security of how it's been set up. They could potentially execute commands right through a search field as if they're physically on the database, which is actually quite scary. So in a lot of places, the website is web-facing. It's accessible on the Internet, but the database is internal and it's not we're facing, so it's secure, but that website has to query the database. So if you've got an insecure database, server connection, web server connection, you can execute commands against the internal database through SQL injection, anything that is within the database could potentially be intercepted. Drive-by attacks are very, very common, especially on malicious websites. This is essentially a download of some software, Dalit of some malware onto somebody's computer because that user has access to a website that essentially was waiting for them to be able to go and download, drive by and download that software onto their computer. Websites are built in website code, commonly HTML, PHP, other things like that. And they could be a command within the backend source of that website to install an execute a particular command. So you going and accessing a website or clicking on something on that website, installed malicious software onto your computer. And then our last one is one that is called a zero-day exploits. What zero-day means is that there is a vulnerability on a application that has not been discovered yet. Microsoft release patches, Apple release patches to fix vulnerabilities pretty consistently. A zero-day exploit is something that has not been made known or made aware to the vendor. So for example, Microsoft, apple don't actually know that these vulnerability exists, which means that there is no fix for this vulnerability. So as soon as Microsoft or Apple or any of these other vendors discover that there is a vulnerability in their software, they would then go and write a patch, right? A fix, and then they'll deploy it. And then of course you then go and update your computer, you update your software. So this is why it's very, very important to make sure that your computer is patched. So you wanna make sure that you update your computer as soon as possible, because that vulnerability needs to be fixed as soon as possible to prevent somebody from using that vulnerability to be able to get into a system. So that was a summary of the 10 most common cyber attacks. There are others, of course, and you can go into a lot more detail about each of these 10. But hopefully I gave you a bit of an overview and hopefully gave me some tips to be able to prevent yourself and perhaps your business from being exploited through these types of cyber attacks.
18. Your Turn: So thank you for watching this class. We've covered a lot of material and hopefully we've given you a good foundation to get the skills that you need to become a great systems administrator, systems engineer, network admin never gained Janine and even other positions outside of that, we've given you a lot of foundations around servers, around networking, around backups, around storage or in the Cloud. Really the skills that I would expect anybody who's wanting to become an IT professional should know at least from a very, very basic level. And of course, your learning journey only begins from here. This is just the foundation, this is just the essential stuff from he, he then moved into bigger and better things and I would recommend that you put some of this stuff into practice. Stuff that we have learnt, put it into practice. Don't build your own environment, build your own lab, build your own service, play around with a service. Build your own networking environment. You could go onto eBay, find yourself some cheap switches, some cheap storage equipment. This stuff is all readily available and you can find some bargains out there to be able to Dick out a little lab for you, whether that be at harm, whether that be in a business, whether your company allows you to do some testing and some training wherever you may work, I would recommend build your own lab and learn yourself because this is just the start of the learning journey. And for me the best way that I learned is yes, watching videos like these in classes like this, where you get a lot of information. But it's one thing to just watch it and hear it. It's another thing to actually put your fingers on it and do it yourself. The best way that I learned is by actually doing it. Sometimes making mistakes. You learn from that, but doing it yourself is the best way that I learned. So I would recommend that for you, go and do that. And I would recommend going back and really watching some of these videos again, because we did cover a lot and lot of information throughout all of these classes anyway. Thank you so much for spending the time. Really, really appreciate it. We'll talk to you next time.
Emilio Aguero, ...all things tech
