the other thing with the supplemental materials I created. A where I grabbed didn't create it, but I grabbed some basically a cheat sheet. Eso. We've shared that out as well, so that will cover some different links with metal you'll find with information that's very helpful if you decide to become a network engineer.
So what is this network engineer thing I keep talking about? Well, it's got many different names. If you go like look at job postings, you'll see primarily it listed as a network engineer or network administrator. You may also see it listed as systems administrator, even though assists Adminis slightly different. But that's where that confusion lies. And that's why we're hoping
this series will kind of clear up some of these some confusion
around these particular job roles in some instances, why We're hoping very much that recruiters watch this video with you, share it with them so they can start giving you good job description as please. So that way you know what you're playing for That way, when he said in an interview, it's a little little more streamlined or not, that was awkward. Questions all the time would be nice
number HK Architects. You may also see it listed as generally a network architect. He's gonna have more
experience. So, you know, someone with, like, five or 10 or more years experience, because they fully understand the networks and what a enterprise level organization would need to do. And then you also may see specialty listings, right? So things like wireless network engineer, cloud network, engineer. Kind of, sort of. Maybe I haven't really seen listings like that,
but you will need to know the cloud. And what kind of talk About that a little later.
By the way, I'm here on the slide. Do not light on. You don't like your routers and stuff on fire. This is just a slide to make it fun. Do not lie. Stuff on fire. It does not solve the problem.
It makes you feel better. Is it does. It does make you feel better. That's exactly what I was gonna say.
All right, So what does the network engineer do? What kind of talk about each one of these. So, you know, you're gonna determine the network topology, and that may be a manual thing. We'll talk about that and how our Duris. That might be or it could be an automated process. You're also gonna be configuring, operating. And, of course, maintaining the equipment on your network.
A good chunk Eager Day is gonna be spent just monitoring, you know, so evaluating the number, traffic and performance
performing backups, we'll talk about some of the different types of backwoods making sure everything you're doing follows regulations or internal company policies maintaining the security of Remember, That's kind of what's the point in having a great network. It's not secure. You know, Joe are myself, could get into it and cause chaos. And then, of course, troubleshooting. We'll talk about some of the commands we can use for that.
So determining the network topology. So as I mentioned you, could do the manual process. So I mentioned last time that the funds story where I got to do Cable Cable Land USA, where I got to go around and find every single port on the switch and where that matched up to every single user in the company. I don't recommend the manual process.
It could be something that you do do in some capacity in a smaller company
at the Enterprise little if you're coming in and you're taking over for someone leaving and they haven't documented any anything, I would actually. She's just using some automated tools to get a better understanding of the network. And that way, make sure excuse me, your life easier
to do some of the manual process so you could do it. You can use any map to some capacity. You can also use different apology mappers, land sweepers, a good one that a lot of people use Just essentially get, like inventory of everything on your network. So again, I recommend the automated process here and not manually going through finding every little
nook and cranny in your network.
And I'm gonna pause for a second here, Joe. Do you Do you have any experience in network engineering? Have you find if you had to do any manual processes? Military? Yes. So, you know, a lot of my stories come from the Navy, including the story for story time today. But
when I was a very young sailor in the Navy, I was I was anyone or any two. For those of you who aren't familiar, basically the lowest kind of couple of ranks you could be in the military Theo office I was in We for reasons that aren't really important right now. We had to
verify that all of the computers were plugged into the right network by hand. We could not, you know, we couldn't just say OK, we've got the audio. We've got the wire shark. We've got whatever capture we had to physically pull the cords out of every single machine and plug them back in to make sure they were in the right place.
The computer system we were working with had
400 computers, I think 4 50 maybe s O. Over the course of three days, I and the other e TEUs, anyone's
crawled around underneath desks, you know, shoved people's shares back, just hunted down every single court in that entire building. And the best part is that there were no problems. Everything was plugged in correctly. It was all where it was supposed to be. But we had to manually check all of the switches and just every single device
because the Navy, the navy dictated it had to be done.
Uh, well, hey. And that's why it stayed perfect, right? And that's a lesson, if you if you like. Joe said. If you're not familiar with military, that's a lesson. And making sure you're on the higher echelon of things get promoted.
Because I've talked about topology. This isn't an example of a start apology.
Now you'll see a lot of organizations down days using hybrid. Actually, most places I know of are mixing different apologies on the network, especially using things like the lands to separate, You know, like Joe myself. So we don't have each other. They're separating us, but we always find a way.
So next, next up, just configuring, operating and maintaining equipment. So as I mentioned, this is another good chunk in your day. You know, this is this is a technology, right? So it may fail. You may have a switch go out. You may have around or go out. You know why those taxes point etcetera? So it's kind of up to use the network administrator, a network engineer,
to go through and, you know, keep an eye on things. Make sure that your equipment is being maintained properly.
You know, obviously, don't eat a bunch of candy or something on top of your servers. where your switches
don't take you no food in the server room. Please, Please don't do that way. I know I've seen terrible situations with that occurring, you know, and that things like, you know, your motives, your firewall, proxy servers, et cetera, et cetera. You know the physical cables that you're plugging in with your network. As Joe mentioned, he had to unplug stuff. Plug it back in that. That's what we're talking about there. So
just understand. It's a network engineer. You're gonna be responsible for managing
from the initial setup of setting it up, configuring it properly, you know, making sure you're changing the default username and password. Please do that. Operating the equipment on a day to day basis and then, of course, maintaining it and replacing equipment as as you need to.
And all that being said, the fun part of all that is when you try to go petition to like the border, you know, the C suite and saying, Hey, I need to get upgraded stuff to say all your budget can't You can't do that. So you know, you have to be, you know, you have to learn that angle, a swell of public speaking and negotiations.
I don't have that listed on this lodge. That's definitely something you want