Imagine you woke up and the news hit you that you're the new systems admin of a particular company!
I know right now what's running in your mind is programming and debugging, and yes, that's going to be on top of your worry list.
This is what you'll be tasked to do;
- Monitoring the system
- Troubleshooting
- Installing software
- Performing backups
- Maintaining local documentation
- Adding and removing hardware
- Automating regular tasks
You sure won't escape the debugging part!
To succeed as a systems admin, you sure have to keep some of these practices in check,
- Be nice, it doesn't cost a penny.
- Always and always monitor your systems. The blame will 100% be on you if any system fails.
- Back up your files, don't wait to treat the patient rather than prevent the disease.
- Another good practice is to keep your users informed. Keep them updated on all the changes.
- And don't forget to implement robust security.
Okay, let's now do some networking. You'll need to know things like a hub, a switch, a router, a bridge, and these are all familiar terms l hope.
Briefly,
A hub is just a connection point for devices on a network.
Switch-connects computers on a network
Router- connects many networks
A hub is just a connection point for devices on a network.
A bridge- connects two sections of a network together.
How do you think the internet gets to your computer??
One may actually fail to break this down but try to decode this process
Router=>switch=>NIC=>device(pc)
NIC being a Network Interface Card that is found in a computer.
With this process model knowledge, please don't run to the router if your internet connection goes down, at least first deal with your NIC and upwards.