I'm concerned about this CCNP change...
I realize this is only my personal opinion, so please don't take it as anything other than that.
IMO, the CCNP seems to have been devalued from a real world standpoint with this change.
For example, I'm still studying off and on for BCMSN. The knowledge I've gained from that study, I've been able to directly apply to 3Com hardware. Looking forward, I was actually fairly excited to get to ONT and ISCW, because topics on those exams (VPN's, QoS) directly relate to things I either do now, or will be doing more of in the future.
As best as I can tell, Cisco seems to have simply eliminated nearly all topics on those exams and essentially turned the CCNP into a pure routing/switching certification. Hell, even this new TSHOOT exam seems to basically be troubleshooting what you already learned on BSCI/ROUTE and BCMSN/SWITCH.
In all honesty, if I hadn't already devoted so much time to BCMSN and if the CCNP wasn't so valuable in the job market, I'd just disregard it, because I feel like this narrow focus has done nothing but limit the scope of this certification. From a practical standpoint, I feel I'll know a lot less when I complete the CCNP now than if they would have kept ONT and ISCW.
Am I the only one who's frustrated with this?
IMO, the CCNP seems to have been devalued from a real world standpoint with this change.
For example, I'm still studying off and on for BCMSN. The knowledge I've gained from that study, I've been able to directly apply to 3Com hardware. Looking forward, I was actually fairly excited to get to ONT and ISCW, because topics on those exams (VPN's, QoS) directly relate to things I either do now, or will be doing more of in the future.
As best as I can tell, Cisco seems to have simply eliminated nearly all topics on those exams and essentially turned the CCNP into a pure routing/switching certification. Hell, even this new TSHOOT exam seems to basically be troubleshooting what you already learned on BSCI/ROUTE and BCMSN/SWITCH.
In all honesty, if I hadn't already devoted so much time to BCMSN and if the CCNP wasn't so valuable in the job market, I'd just disregard it, because I feel like this narrow focus has done nothing but limit the scope of this certification. From a practical standpoint, I feel I'll know a lot less when I complete the CCNP now than if they would have kept ONT and ISCW.
Am I the only one who's frustrated with this?
Comments
I agree with you though, I deal with that stuff somewhat day-to-day, apart from QOS and the thought of getting to ONT and ISCW had (still does) excite me, so I won't give up just yet...
Working on renewing CCNA!
Sure, they've added a troubleshooting exam so you can't "get lucky", so to speak, but it seems like that exam is simply validating ROUTE/SWITCH level knowledge, as opposed to actually teaching you anything new. Isn't that the entire purpose of taking those two exams to begin with...to validate your knowledge?
Unfortunately, the CCNP was a lot more practical for me before the change. I don't, and most likely won't for the foreseeable future, work with a lot of in depth routing. That's not to say I don't want to learn, but it's much harder when you don't get to apply the knowledge at least somewhat. It makes the studying seem completely irrelevant.
Before, BSCI was just going to be something I had to endure in order to get my CCNP and learn the other technologies. Now, routing has essentially become half of the exam.
I'm just confused and concerned. I almost don't even want to bother with this cert anymore, but I feel as though I'll doom myself to never really moving ahead unless I obtain it.
For me the CCNP is the core networking certification, which is routing and switching at its heart. It should not try to fully cover it all at the expence of depth.
You now have the CCNA tracks like Security, (which has many of the topice from the old CCNP exam) you have the option of getting a deep knowlage of core networking in the new CCNP and then by taking one or two extra extra CCNA's which are single exams, demonistrate knowlage in other areas.
of course if the CCNA tracks are not enough, you have the other CCNP level certifications to show off with.
I think seeing as how large the networking field now is, the new CISCO certifications give you a great ability to pick and choses how to show of you skills. And once you have a few under your belt, it will give a would be employer a much better view of your areas of strenths.
AS far a the trouble shooting goes I think this is a great addition. The other two exams are to show you have the knowlage of the technoligies, but we all know that much of what we do in our jobs is trouble shooting and problem solving. After all a employer dosent want to know jsut if you know something, but how well you can apply that to something out side your comfort zone, and how you can adapt.
I dont use routing in my day to day job much, I am much more focuced on switching, so the CCNP Routing exam will give me great optunity to practice and expand that field. Ok not important for this job i am in now.. but then again I might want to change it one day, and that will be a lot simpler if I can show I have Strong, rather than Basic routing skills.
I can't agree with that,
Most of the topice in CCNA security and some in the CCNP Switch are ones I haven't be exposed to through work, or am lickly to be. But I have a Lab / simulatior set up and I play around most nights.
To be honest my home lab is more feature filled than the network I work on. Ok it may not be as big, or have many devices attached, but thats the joy of networks, the fundementalys can be configures on a small lab network, that directly scale to enterprise size networks.
I don't think you need to apply the knowlage in a work situation for it to be relevent to your over all skill level.
So I think it's actually a good step to cut out the chaff. They've created other full certification paths for the other technologies. So while they may take away some of the ability to appear as a jack of all trades, it'll make you a better R&S engineer, and that's something I have no problem with. I deal with enough bad engineers that I'd kill to get some folks who've cashed in their cluepons on the other end of the phone
Well, sheesh. Routing *is* kind of important, you know. The packets don't move around by magic. Determining where and how you move traffic is as core as it gets, without that, the other technologies are pretty useless
Like people have mentioned you will be able to study the material in other tracks and hell get another cert whilst doing it.
From someone like myself, who is looking towards a possible future goal of the IE R&S, im releaved to see a troubleshooting section in there as it should help prepare towards the more advanced troubleshooting in the v4 of the R&S now.
Only thing you can do is either finish the exams before the due date or start on the new track - simple as that.
Bsc (hons) Network Computing - 1st Class
WIP: Msc advanced networking
The ISCW is more or less an SDM exam. It's garbage, but I am enjoying it in the most part.
sorry i disagree with you. Knowing how to configure an IPSEC and GRE tunnel is a huge plus in a network engineers arsenal, many companies run GRE over IPSEC to save thousands of dollars monthly.
2023 Cert Goals: SC-100, eCPTX
Very nicely put.
At the end of the day you have to take it upon yourself to learn the technology. For example, the CCNP really doesn't cover layer 1 stuff, but if you needed L1 for your job, wouldn't you learn it? Or would you just skip it because it's not on the CCNP?
i do felt however the CCNP should have been 5 exams i mean keeping the 4 they had and add the troubleshooting exam, its only fear that if you are a ccnp you know how to troubleshoot and not jsut how to configure, cause in the real world everything that shouldnt fail, fails.
Surely you don't assume that I was discounting the importance of routing as a whole, as that is most certainly not even close to how I worded my previous posts. I was only making note of the fact that *I* don't deal with in depth routing in my day to day job. Considering it's fairly well known that information not often used has more of a tendency to be forgotten, it stands to reason that my concern lies in studying for a certification that is roughly 50% routing, only to not frequently use the knowledge and have it escape me.
However, I do appreciate you enlightening me, as I was always predisposed to believing the packets did, in fact, move around by magic.
That's kind of where my opinion was stemming from. Being able to apply QoS and having the knowledge to create and manage client access and site to site VPN's is, IMO, crucial to managing even the smallest of networks anymore. You know how I said I don't deal with in depth routing? Do you know how many sites I visit that run QoS and implement some sort of VPN? It would be easier to count those that didn't and among all these sites, I've never ran into the need to configure or troubleshoot OSPF or EIGRP.
When I think of a "Network Professional", I think of a well rounded individual who has experience in multiple areas. Kind of what the current version represents. As it stands now, it just seems like Cisco simply chopped off information and added no new material, but simply an exam to further validate what you'll have already been tested on. It seems like this TSHOOT exam should have been made an R&S specialization or something, while keeping the CCNP broad.
But, you know what they say about opinions.
Sure, but people make a bigger deal out of this than is really necessary. Sure, it's useful knowledge, but it's not going to make or break you as an engineer. It's just a few more knobs to turn, and not really essential ones at that.
Ok, so if you're not going to do R&S, don't certify in R&S. And yes, you certainly did seem to be marginalizing routing as a whole, as you were complaining that routing now comprised half the certification.
Yeah, unfortunately, J.K. Rowling's forthcoming series of books from Cisco Press has been put on hold indefinitely due to this discovery.
And do you have any idea how many networks I've touched where they're not doing VPN on the router (which is stupid in my opinion anyway!). Usually it's either a dedicate server, or dedicated appliance. SSL VPN is also becoming more and more prevalent, and there's nary a mention of that in ISCW. It's all about being able to configure EazyVPN from SDM, and then do some tweaking of IPSEC from the CLI. In my opinion, this is hardly best practice and can lead to some lessons that will need to be unlearned in the future if you *really* want to be good at your job. It's just another example of Cisco trying to cram too much into the CCNP, and doing a half ass job of it.
I mean, let's talk a bit about GRE over IPSEC. Great in concept, and a very useful tool.
Go look at the ISCW Exam Cert Guide if you have it. Their *entire* idea of teaching a network 'Professional' to configure a Secure GRE Tunnel....... is to use a wizard. Really? Seriously? That's not good training. I haven't taken a look at the most recent edition, but I'd be willing to bet I could get a better solution out of O'Reiley's Cisco IOS Cookbook.
ISCW, and to a degree, ONT are *horribly* executed exams. ONT isn't as bad as ISCW, as it's QoS coverage is actually pretty good, but it fails in that it's Voice and Wireless coverage is just absolute crap. ISCW is just bad all around. For both exams, the technology they cover will pretty much require you to learn more than the exams cover. I guess that's great if it provides a Catalyst to learn more, but under the current certification, if I saw CCNP, I wouldn't assume they knew dick about VPN's, because if I point them to a server running, say, OpenVPN, and tell them to set it and the network gear up for client VPN termination, I don't think they could do it, unless they're already familiar with the software invovled, or without a good bit of time spent on Google. The only things I assume a CCNP can do pretty well are IGP's and most layer 2 stuff. But I may be a little bit cynical about it, since I've been through it and know what to expect.
Keeping the CCNP as a jack of all trades is a bad idea when they're busy creating new certifications to deal with focused areas, and they're all training pretty well to deal deeper with their respective technologies. That, IMHO, devalues the CCNP just as much as you seem to think that pulling content off of it will do. Cisco is sending a pretty clear message - if other concentrations are what interest you, go certify in that. They are obviously intending the CCNP to be the routing and switching specialty, and I wouldn't be surprised to see them change the name to reflect that.
For a start the BCMSN topics are hardly in depth at all, I been going over them to prepare for the SWITCH exam and I really hope this goes a lot deeper, at the moment its just skimming the surface of what I think of as the switched environment.
In my view the CCNA level is there to show you have over all basic knowlage (and when i say basic I don't mean simple I mean good introduction to a topic.)
The CCNP should show you have a good indepth, understanding of a topic.
what some people seem to be suggesting is that the CCNP should be the same, as having all the CCNA certificates.
If you take the ccna voice, security, wireless, and design then you knowlage is not going to be that different from the old style CCNP.
IF you look here
IT Certification - Cisco - Cisco Systems
you will see the CCNP is only part of the Router + switching path and the storage path. the security, voice, wireless and design already have there own separate profsional level certificates. So as Forsaken shugested, the CCNP is a switching and routing certification. it is not general "network" knowlage any more.
There not going to split switching and routing up as these are the "core" networking concepts. And do go hand in hand. But I for one am glad they have gone in to more depth.
But I'm also grounded in practicality. The reality is that the level of training you're expected to do to be able to pass those additional subjects is laughable, and not always translatable into real world skills. The VoIP and Wireless sections are pretty much just trivia, if you want to seriously deploy those technologies, you will need more training than what the CCNP expects of you, so in that vein, I regard the CCNP coverage of those topics as worthless.
Folks just seem to give the exams, ISCW in particular far far too much credit.
Wait, rewind real quick. They DONT move by magic?
:study: Current 2015 Goals: JNCIP-SEC JNCIS-ENT CCNA-Security
Hilarious.
I know, right? It's called Ethernet! That just screams magic! (or drugs, which I suppose are magical in their own way)
Ether-what?
I do this to the network guys at work (I'm more of an Intel guy myself; but have self-proclaimed basic/intermediate networking knowledge). Its always fun when they take the bait...Luckily TE is much smarter
K, my tangent is done; sorry guys.
:study: Current 2015 Goals: JNCIP-SEC JNCIS-ENT CCNA-Security
Now, if you want to know how to set up a VPN, what's stopping you to learn it by yourself? Or is it you don't want to learn something if there is no certification at the end?
Yeah, pretty much. You can never stop learning if you want to stay alive in this game, let alone get ahead.
Yup, that's why I branched out into DP and IP as well. I have a sneaking suspicion that at some point I'm going to have to at least get very familiar with the CCSP material, even if I never take the actual exams. I just hope I can avoid getting dragged into Voice.
I did say more or less
Perhaps my wording was too strong. The exam is fine, great content, MPLS and IPSec for example. I will admit the SDM is easier though, so perhaps I should just quit my whining
I think I will do finish the BSCI and BCMSN and then TSHOOT to get the cert and rthen will check out both trainsignal and Testtout materials for ISCW, and probably ONT too.
I read most of the CCNA security certification guide and i thought it was plain boring.
I disagree, I just finished mine and it gives good entry level to firewall, IPS, VPN's and switch based security. as well as the standard info on types of attack.
in fact the only real difference between it and the ISCW seems to be the MPLS, and cable/DSL connections.
Then again I didn't read the guide and just learnt it from the blue prints.