Studying for a certification teaches you a lot about h= ow to manage the product you are working with, but unfortunately there is a disconnect between knowing how to manage a product and managing a network. = One of the fundamental jobs of a network administrator is to maintain the netwo= rk in such a way that if something happens to him/her, the knowledge of the network can be easily picked up by a qualified replacement. All too often though, administrators skimp on documenting processes and procedures in fav= or of keeping the information in their head. While it might be difficult to al= ways find time for boring chores like documentation, not doing so is akin to spending three days working on a big spreadsheet, never saving, and then ha= ve the power go out on you. Sure, you can recreate the work, but at a signific= ant time and potentially monetary cost.
Recently, I resigned from the company I was working at= in order to take a position with another company. My replacement walked into a situation where every server, switch, router, patch panel, printer, and workstation was documented. That was a far cry from when I inherited that network from a previous administrator. Likewise, the situation I walked int= o in my new position has had me spend the better part of my first three weeks ju= st diagramming the network and server infrastructure, knowledge the previous administrator stored nowhere but in his head. This has resulted in inefficiency, and delays in getting problems resolved. In some cases, certa= in people know a little bit about a certain aspect of the network, and with software tools and talking to various people I can piece things together. In other cases, no one knows anything about another aspect, leaving us with lo= st knowledge and having to reinvent processes that were already in place.
So what does this have to do with certification? See, certification studies teach you how to administe= r a network, but it doesn’t teach you how to be a good network administra= tor. Being a good network administrator means that you have to have the technical skills that certification validates, but just as important is having the ri= ght mindset and attitude towards the network administrator role. It isn’t just about documentation. It is about having the mentality of a shepherd. T= he company relies on you to put the network in a position to work today and tomorrow, but that’s not where it stops. You also have to ensure that= it will work beyond your tenure with the company. While you can’t physic= ally be there once you leave the company, you can leave your knowledge behind by= not only documenting your processes and procedures, but by sharing your knowled= ge with others that you work with. Some people fear that if they don’t h= oard their knowledge, then they can be easily replaced. That simply isn’t = the case. That is, hoarding knowledge will not protect your job. If a company w= ants to get rid of you, they will find out a way to get the knowledge or work ar= ound not having it.
The bottom line is, network administrators are paid very well in relation to the general staff in a com= pany for a very good reason. We carry a much greater responsibility to the well-being of the company’s present and future. It is a responsibilit= y we can’t overlook as we study for certification exams and focus on the day-to-day administration of the network. We have to go beyond the technical side, and realize that the technical knowledge we possess is worth much les= s if we don’t ensure that it lasts beyond when we leave.