Networking career path

[Ghiedo27]

Right now I have a CCNA and I'm looking to build my skill set. It's my understanding that you really need something like 3-5 years of experience to be taken seriously as more than just a paper tiger CCNP, so I'm wondering what I can do in the meantime while I gain work experience.

So far I've been looking at the MCSA for server 2008, CCNA Voice, Learning a bit of coding (PHP?), and maybe network storage. I don't want to spread myself too thin, but I want to be moving forward.

Any opinions on this list or anything to add? I want to stay on a networking track, but I want to be flexible enough to handle a real working environment for a network admin or similar position. Thanks in advance.

 

[Railgun]

So, I'm going to sound like an ass I'm sure, but if you search this subforum for network career, you'll find 59 threads on the subject. That's a good start.

 

[Ghiedo27]

That's a perfectly reasonable thing to point out. No offense taken.

Unfortunately, I'm just finding conversations about certs or college being good/bad for the most part. I actually got the tip on learning PHP from one of the earlier threads and was hoping to get more information about valuable supplementary skills.

 

[ViviTheMage]

Do you have any work history yet, or are you going to be fresh into the field?

IF you're fresh, you need to start somewhere, low on the totem poll and get your IT skills going, before you can dive right into networking, and touching production gear.

 

[Red Squirrel]

Do you have any work history yet, or are you going to be fresh into the field?

IF you're fresh, you need to start somewhere, low on the totem poll and get your IT skills going, before you can dive right into networking, and touching production gear.

This. Start low and work your way up. Help desk at a medium/big company is probably the easiest place to start. They'll have a PC support dept, server dept, network etc... so you can move your way up or go straight to network. (server and network are usually equal, but it depends on the company's structure). Usually it goes level 1(helpdesk) level 2 (pc support) level 3 (server/network). Working at the help desk will also let you see lot of different aspects of the company so when you do end up applying for an internal higher end position you have a better idea what that position entails.

 

[Ghiedo27]

I get that experience is the top priority. I'm just looking to work on the skills that are going to pay off in a few years when I'm looking to move up. I'm hoping to get a broader view than what I'll get from one workplace.

Certainly I'll pick up what I can as I go, but I don't want to rely on what fits in with a single company. There may or may not be any positions at company A, so I want to be able to appeal to companies X, Y, and Z as well.

 

[ScottMac]

Part of the solution is to figure out what opportunities are available where you are (geographical location) and where you want to go (if they're different).

One of the reasons you may want to find entry/basic work before or during loading up on training is that you can see, from a true & practical perspective, what kind of skill-sets are needed in your area ... supply/demand principals apply. If you're lucky, what's desired is something you're interested in; you learn faster, retain more, and are likely to be able to apply your skills in a more intelligent fashion.

Also, in addition to hardware & protocols, look into some useful software ... learn, in-depth, applications like Excel, Access, PowerPoint, Crystal Reports, mySQL / Oracle, and MS Word (to the point you can create a standard business report document).

If you are aiming for network maintenance and management, you may want to investigate applications / tools like HP Openview, MRTG, and WireShark.

Helpful, but not strictly necessary are some scripting languages like Perl, Python, Ruby, TCL ... all available for free, with tutorials, from ActiveState.com. Some folks are also partial Virtual Basic for application creation and scripting .. I've never used it myself, but many find it useful.

The point is to not concentrate only on networking technology, unless you can find a job that deals ONLY in network technology. Brush up on your writing skills ... knowing there's an issue means nothing if you can't effectively communicate it. Understanding how applications interface with the networking structure will help you to troubleshoot and design a more efficient network.

WireShark is extremely useful to see what's actually passing "on the wire" for diagnosing things like slow response (bad cable, overloaded server, or poorly written/implemented application?). It's also free and well-documented from wireshark.com.

Some of this stuff you can get into casually, and learn a little at a time as you learn other stuff.

Getting back to my original point (sorry to ramble), find out what's needed, and of what's needed, what you like to do, and where do they overlap. Regardless of your focus, diversify your knowledge, as possible, to include the other aspects of the network you're working on.

 

[talion83]

What ScottMac said is very similar to what I was planning indicating. If your goal is "networking" in today's environment I would say that it should have a lot of security based around it. Unless you are in a very large company that has a separate department for security, then Network Security is going to fall to the Networking Admin.

Wireshark is a great thing to learn. But to a degree I would say learn how to penetrate your own network - not necessarily the machines on them, as much as the way to get TO the machines on it. How do you monitor for what traffic is going out/around your network?

With everyone constantly being hacked and more things moving to a 'cloud' environment, the big thing that companies need out of a network admin is someone who can set and monitor security policies (auditing of course being a bit part of that). The Auditing is probably where you will get into more scripting.

 

[alkemyst]

Right now I have a CCNA and I'm looking to build my skill set. It's my understanding that you really need something like 3-5 years of experience to be taken seriously as more than just a paper tiger CCNP, so I'm wondering what I can do in the meantime while I gain work experience.

So far I've been looking at the MCSA for server 2008, CCNA Voice, Learning a bit of coding (PHP?), and maybe network storage. I don't want to spread myself too thin, but I want to be moving forward.

Any opinions on this list or anything to add? I want to stay on a networking track, but I want to be flexible enough to handle a real working environment for a network admin or similar position. Thanks in advance.

First, if you can speak to CCNP, no one is going to call you a 'paper CCNP'. If you got it by braindumping then you are screwed.


Voice/UC and security are huge needs right now.

CCIE is a path that probably is the best bang for buck in the market. Most could do this (if it's really their passion) in 18-24 months if they dedicate the time needed.

 

[mammador]

Go to any firm that involves networking/TCP-IP.

I have a friend who designs security systems (not computer security, but cameras, electronic locks, etc.), and he uses his CCNA to assist in that.

CCNA would get your foot in the door though, and you would need a couple of years experience to get a CCNP. From there, you can probably get a network admin post at an medium-sized organisation. CCIE is largely a crowning achievement type of cert, and requires a lot of experience to attain (working wise). I'd think it's largely senior managers and/or ICT directors who have CCIE.

 

[alkemyst]

CCNA would get your foot in the door though, and you would need a couple of years experience to get a CCNP. From there, you can probably get a network admin post at an medium-sized organisation. CCIE is largely a crowning achievement type of cert, and requires a lot of experience to attain (working wise). I'd think it's largely senior managers and/or ICT directors who have CCIE.

Many CCIE's have no desire to be management.

 

[soholingo]

My take is going to be different from most but my focus has always been to get into the action, and make as much money as possible.
I would NOT start at the helpdesk unless you want to learn how to service people and fix broken printers and teach people how to indent. If you are sharp and can understand the concepts you need to do the following:

1. Build a lab at home that you can build to mimic a work environment. Its networking so you better be able to get your packets where you want them, and when you can't you want a test environment to show you what could go wrong. Having a good lab is a LIFE LONG requirement.

2. Get a job as a network admin, NOT help desk. Send your resume out to as many recruiters as possible, make sure your CCNP is prominent, and have them get you the job you want. I would take ANY job that let you get your hands on networking equipment. Do a lot of interviews, find out what people want, and then get a job as a network admin.

3. Even if you don't know what you are doing, you will learn from your mistakes.

4. Decide on whether you are going to work on systems (OS, applications, etc...) OR networking. They both involve security so you can work on those concepts too, but decide if you are going to do networking. If so don't waste your time on learning databases, scripting, etc... If its not helping you to get packets from point a to point b, with the security and performance you want, then its wasting your time. Let the system guys do their job you do your job.

5. The biggest thing is to not be afraid. You are going to know some things others don't know and they will know some things you don't know. The key is to get into the deep end of the pool. If you mess up something so what? Get another job and learn from the mistakes.

6. Lastly do work that will get you your CCNP and then your CCIE. The CCIE will get you money, experience and the high level work you ultimately want.

Good luck with it!

Jay

 

[alkemyst]

Good points soholingo.

However, in networking learning TCL (pronounced Tickle) is a great thing, most CCIE's learn it eventually.

I agree though. Focus on networking don't try to be a jack of all trades. You will pick up a lot of side skills along the way already.

Working HelpDesk is a dead end and also will limit your salary if you plan on staying in the same company.

Definitely the CCIE is the way to go. Some never get it.

The most anyone has taken the test is 31 times now I believe. The average is around 7 times. At $1500 a pop + airfare and travel + books/materials/lab time/lab equipment it's an expensive journey.

However, bang for buck I personally feel it's the best right now.

 

[soholingo]

However, in networking learning TCL (pronounced Tickle) is a great thing, most CCIE's learn it eventually.

I agree though. Focus on networking don't try to be a jack of all trades. You will pick up a lot of side skills along the way already.

We are in agreement. The key point is pick up those ancillary skills on an as needed basis, -don't let it be the focus.