so some different tools. There's a lot of those out there, you know. A lot of them are based around the performance. Know what model it? Monitoring, Analyzing wire sharks. Akama wanted you. So Joe mentioned it with the sys admin. It's a great way to see, you know, I'll say packets, but basically the information
that's going across your network. So it's a good way to look at that information.
See, you know, is it something bad? Is it coming from about I P address again? Don't worry about the terminology that we're using in this intro course, but, you know, is it a bad I P address? Is there something wrong with the packet or the information, you know? Are we giving away information? Right. So are we seeing that when we look at some information, we're seeing that user names and passwords
are sitting right there for if somebody's watching this,
they can look at that information and then get my user name and password. So all these things are part of a network engineers job of you know, not just monitoring the network, but also protecting it
many different commands that are commonly used, Our tracer and windows or trace route in Lenox Systems. The Ping Command is it is a huge one, and it's look up I p config or I f. Config. If you're using Lennox and then also net stat as well.
We also want to test our network bandwidth, right so we could do that. There's different monitoring tools out there, but we could also just do it. Different websites like Speed test dot net or as many others. And you may be familiar
at your home network, like, you know, from the cable company or something that there's a website when you call them for support. You know, I recall that sys admin for support. They can kind of talking through how to go to a certain website. They'll have you checked the speed of your connection, and then from there they can help troubleshoot a little more. So that's essentially what we would be doing with a site like speed test.
We want to see the bandwidth or the
you know, the kind of the thick of it, like your car, like how fast your car is going right, So think of your speedometer. So if we've got a really fast car like a Lamborghini Ferrari or something like that. We could do a lot. We could go to things a lot faster, right? So we could go to the Internet a lot faster now for driving like a little putt putt car. You know, that's
really beat up and everything like that. It probably can't go that fast, right? It's leaking oil and stuff like that. So
that's kind of the same. Kind of like what a speed test is right? So we're essentially hoping that we have that Ferrari or Lamborghini. But we also want to make sure that our network is not that little beat up. You know, junk car that we used to drive like in high school.
I have both metaphorically and literally driven that car. Many, many, same here. Same here as many of
calculator is another thing that more advanced on the number of engineers used just to make sure they're getting the appropriate I. P address Party is good for, like sshh connections on telling that connections to make those little more secure. And then, as I mentioned, you know, there's there's a whole lot of different network performance and analyzer tools
Ah, lot of scenes, which will kind of talk about a little bit when we go into incident response. In just a moment,
a lot of scenes will have all this stuff kind of wrapped up into one so you can monitor your network. You could look at the traffic. You can look, you know, settle different alerts on there to report back to you as a network engineer of what's actually going on with your network.
Typical day. So I mentioned, you know, reviewing logs, right? That's a huge part when I can't say it enough. But that's why we have those different, you know,
devices, right, that they could take all that information in that we're getting on our network and then basically, based on what we tell it, that can spit back the appropriate information to help us make better decisions about the network and also allow us to generate reports that we can use to take the like management or whomever to kind of petition our case
rebooting devices. So, you know, let's say a server is acting up or something like that. You know, once you've exhausted your trouble shooting or you may know from experience like I just need to reboot this virtual server real quick, and that should clear everything up, you know? And that's one of things that you may do
fixing different issues. So different issues are gonna be reported or escalated from the sis at Mintz. I'm saying, Hey, this year that's going on. You know, I think there's an issue with this server or this workstation. You know, these are the things that are going on, you know? Can you take a closer look at this? So a lot of that's gonna be fixing issues or troubleshooting performing backup. So a lot of times, this is automated
in organizations, as it should be to some extent.
But also, you want to make sure that you are monitoring or getting an alert about the backups to make sure they're actually being done. I've actually worked with organizations that thought the backups were going, and then once the ransomware attack occurred, they realized that the last backup was like, six months ago, so they lost all that data from that attack. So
keep that in mind if you're gonna work, it's a network engineer. Back up, back up, back up.
It is kind of the great thing there, so just make sure you're back up the information. Ah, good thing as well. Just for on you're on your own computer, right, back up information to the cloud or to an external device. So that way, if you something happens on your computer, then you can actually, you know, re image it or just take that information to a new computer and keep working
as a brief anecdote on that on the note of backups, I had the worst professional day of my entire life. The organization I was working for, our primary server went down, and I found out that no one had backed it up in more than a year. Nice. So I got to spend the next 17 hours with a forensics tool kit
combing through that server, trying to get as much data as we could back.
So yes, your stuff up or I will haunt you,
you know? And as you mentioned, it's never fun. Especially, you know, forensic tool kit sounds like super cool, but it's a lot of work to use that to comb through parts of files, and I'm very, very time consuming as he mentioned. So yes, back it up. So if you decide work is a network engineer or even assist, admit or anything in general,
I just always scream out, Back it up,
everybody People get sick of hearing it. But guess what? The Remember in the back stuff up. So they'll actually be like, Hey, I'm backing it up. Leave me. Look s 01 thing you guys can try access control less. VP ends another thing. You'll be configuring different VPN also segmenting networks. Looks like the land and stuff like that
again. None of the terminology that you need to know right now
Unless you decide that you want network engineering as kind of a career path.
Now, then, most importantly on this entire list besides reviewing logs documentation a CZ we got to talk about with reporting communication, make sure you're documenting everything generating documentation, you know as faras, mapping out networks documentation for reporting. So that way you can petition your case in front of management or whomever,
and then also so you can stay organized and understand what's actually happening
with your network. Because the network should be telling you a story. Hopefully, it's a good story could also be a bad story of like, Oh, my goodness, we're under attack. But at least it's you telling some kind of story, and so you you need to be mindful of how you can get that information and learn the story of your normal quote unquote normal network activity. So that way you could look for abnormal things that are occurring.