| Author |
Is it worth me doing my CCNP without much experience?
|
|
| Spides 2002-10-30, 4:22 pm |
| Do you think it is worth it? I don't have much experience, installed a couple of switches and a router into companies. Recently got my MCSA, but I am out of a job at the moment. I am in Australia doing voluntary work, will it be worth having if I am trying to get into that field.... | |
| ssimpson53 2002-10-30, 7:41 pm |
| I would go for it man. I went through the same thing a few years back and went ahead and spent some loot for a CCNA class...did some studying and got certified. I believe that the Cisco Certs pay for themselves a lot quicker than micro$oft certs do. Of course you should probably like working on the WAN infrastructure stuff if you are going to put forth the effort because that is where you will end up if you get this cert. Just my $0.02
-w00kie
"stop bitching. start evolution." | |
| peterd 2002-10-31, 6:38 am |
| Hi Spides,
yes, go for it!
Without experience you'll probably not get a great job first time out, but you should be able to land something that will give you the experience that you need to get a better job.
You may have to change jobs after, say, 12 months work, but each time you'll be improving you position.
As for working on WANs (as ssimpson53 suggests) I reckon that's a bonus!
A PC Support tech gets loads of user hassle while a WAN tech generally doesn't talk to users, there's no hassles. PC users will always find some way of screwing up the simplest system that you give them!
It's a bit like the difference between being a bus driver (carrying passengers) and being a lorry driver (carrying cargo). Get the cargo (data) to the right destination any way you can and no-one complains much!
Regards
Peter | |
| pseudocyber 2002-10-31, 9:43 pm |
| I don't know about a WAN guy not having any hassles!  We have an ATM WAN with a Frame Relay backup and also support ISDN and VPN as well as multiple LAN's. The hassle we have to deal with is developers putting software one servers that isn't designed with networking in mind and then when them and the users start testing and working on it and they don't get the performance they thought they would and start blaming the network and having to prove the network's innocence and finding the problem on their software. Talking about hassles - using a sniffer and trying to use packet traces and explain them to people who are clueless and get them to understand that it's their app ... argh!!! (gnashing of teeth). | |
| bernardsim 2002-11-01, 12:14 am |
| HI Spides,
Go for it if you intend to stay in IT line. Even if you don't it will still benefit you.
I know 4 papers sound a long way to go but
focus on 1 paper at a time will be more encouraging.
Just Do It!!!  | |
| peterd 2002-11-01, 6:27 am |
| hi psuedocyber,
you talk to users!
it's obviously a different set-up here but I report to the IT manager and no-one else. And if I tell him he's got a problem somewhere other than the network then he believes me.
Anyway, packet traces are the fun part of the job...
regards
Peter |
|
|
|