my first job as a network administrator - need advices
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
my first job as a network administrator - need advices
This is my first job as a network/system administrator in an real environment.
The actual Admin has just given me the root password and explained me about the network infrastructure. He will quit soon.
Please, give me some tips ! Where do I start from? What must be my first steps? What are most important first things I must do as the new admin? What are the most important things that I have to have clear in my mind ?
I have the opportunity to study the network and the servers for a few days and then we (I and the admin) meet again to clarify what I didn't get clear in my mind. I after that I am on my own. I don't want to miss something and to get later into troubles. Every important aspect must be clear after we meet again.
I can't say that I am new to linux, but I've just used it at Home for my personal needs not as job in a read company. I have good knowledge about networking and OS (linux), but not so much experience.
I had the same situation happen to me 3 months ago. All I can say is read up as much as you can. And work with the a server in a test enviroment so you can figure everything out. If you can get good at setting up a network with 2 pcs, you can do it with 50.
First thing I would do is read through one of those books you are going to get and change the root password. Also do a check through the /etc/passwd file and see if there are any user accounts with a ¨0¨ right after the :x: or :*: fields. Then I would start doing all of the nitty gritty reading. But then again, I am a newbie.
More seriously, if your background is development, you must be prepared to find that the source of your troubles will usually *not* be technical, thus technical responses are only workarounds... The solutions are human. Always. Well, almost always...
I am not an Admin, only studying for that sort of position in the future. But some advice I can give is, lots of paperwork, if your a programmer you should be quite familiar with paperwork. Document everything that happens, and everything that is requested to you by others, that way, if trouble arises someone else higher up had to OK'd it first, may just save your skin. Have an Acceptable Use Policy for the internet/network enforced and signed by everyone in the company if one isn't in place already, workers need to know what they can and cannot do on the network.
Being a System Administrator myself, this is my advice to you:
Security, security, security!! The last thing you ever want is to tell your boss that a cracker did this or that. It's your job to keep everything as up to date as possible, and do your best to try to break into your own network, so you can figure out how you can monitor / prevent it from happening.
Another bit of advice... "measure twice, cut once". In the computer world, test it before you do it live. Get a machine and set it up like another one that is on the network, and install stuff, uinstall stuff, duplicate problems, anything you can do. Format it, install windows, reformat it, install Linux, format it again and do a dual boot. If you ever need to do something on someone's computer, you have a place to do it first and will know with a lot more certanty that it will work when you do it on their machine. People get really grumpy when "the big tech guy" comes in and messes everything up.
And, if you have the authority, make very strict policies on what people can have on their computers. The last thing you want is Kazaa or other P2P software causing network lag, spyware infestation, and employees spending more time looking at porn then doing their job.
I totally agree with cormander. I do most of the things he mentioned. But depending on the network enviroment you have, take full advantage of it. I hate windows more than anything but I work for a company that developes software for it and the support people need it loaded on thier machines. It was written horribly so all pc's with it installed need local admin writes to run it. I have a win2k3 server domain and the workstations that don't need local admin writes get locked down with GPO. They can't install anything, not even winzip. Point it, use everything to your advantage to tighten things up. I wish I was able to run a pure Linux and Unix enviroment but I can't, so I take advantage of some of the minor benefits of other O.S.'s.
Distribution: Slackware / Debian / *Ubuntu / Opensuse / Solaris uname: Brian Cooney
I dont know if your used to using the CLI or GUI, but get very comfortable with CLI. although GUI stuff has come a very long way, CLI tools are still more mature, and less likey to muck up. Also, if you can do it via cli, you can do it from any computer that can route to your network.
Its always a good idea to save a backup copy of any config files you are going to modify on the server as whatever.old or somthing like that, so if you make a mistake you can dump the old, working config in until you have time to read threw and find your error.