Slashdot Mirror
CCNA Certification Library
Although it is possible to enroll in official ICND and INTRO courses created by Cisco, the books that make up this "library," apparently, are not the books used in those courses. Within the ICND book, Odom refers to "the ICND course, on which the exam is partly based," suggesting that what you have in your hands is a reverse-engineered study guide: a study guide for an exam that is based on a course that does not use said book. Odom occasionally presents tables that he claims come from the ICND course. Clearly, some parts of the course are not fair game for the study guide.
In other words, don't think that just because you are reading the official Cisco press CCNA study guides, you are dealing with a set of information that is as close as possible to the set of information from which the test was drawn.
Studying these books will prepare you for the CCNA in the same way that reading the Encyclopedia Britannica from A to Z will prepare you to identify the capital of Nairobi. It goes without saying that a CCNA candidate should not be studying just to pass a test, she should be studying to qualify herself for a job. But in this case, the difference between the material presented and the material actually making up the test is excessive.
Odom goes to a lot of effort to make the reader feel like he is being spoken to by a friend. "Fun, isn't it?" he writes, after presenting an illustration of function groups and access points that I had to re-draw for myself several times in order to understand. Later, he describes Inverse ARP as "another case of learning by listening, a great lesson for real life!" Gee, thanks. The subtle condescension in the non-humorous asides, the gleeful overuse of exclamation points, and the fable in which Pebbles Flintstone invents networking is compounded by the persistent contextual encapsulation of every single topic in the book. Odom tells you what he's going to tell you, then he tells you, then he tells you what he's told you, much more than necessary.
A better way to put the flustered reader at ease might have been to proofread the books. The ICND guide, especially, is so full of typos that it is often embarrassing to read. In some cases, these are nothing more than obvious misspellings that can be passed over without much more than a little annoyance (e.g. ICND p. 472, "status enquiry messages"). In other cases, the meaning of the sentence is muddled. Worse, the configuration examples have obviously not been proofread either, resulting in, for example, the prompt "R1(config)#" when the appropriate prompt is "R1(config-if)." The difference may seem trivial, but understanding its significance is the kind of stuff the CCNA is all about.
Each book comes with a CD containing a practice test engine and a router simulator (both from Boson). The mistakes in the ICND book pale in comparison to those in the CD test engines. In fact, an argument could be made that studying with those practice tests will hinder more than help the CCNA candidate who has not read the books thoroughly enough to recognize the mistakes. Many multiple-choice questions count correct answers wrong and vice versa (and some of these are taken directly from the books, which usually give the correct answer). A configuration entered into the CLI on a simulator question will be graded as wrong, and the user will then be presented with an identical configuration as an example of the correct way to solve the problem.
None of these problems change the fact that these books will, if used correctly, absolutely help you pass the CCNA. But do it this way: Read the INTRO book. Take the exam right away. If you don't pass, flip through the ICND book and find the areas that you actually need to work on. You'll save months of study time that could be better spent working on your CCNP.
I give the library as a whole 3 out of 5 stars.
You can purchase the CCNA Certification Library from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
I mean, come on now. If this networking novice can pass a test for a networking cert then the value of that cert is substantially reduced. The CCNA is almost as worthless as the MCSE and A+. Any schmuck can get their MCSE.
Amazingly enough this article post coincided with my yearning to improve my understanding of networking and computers in general. In the past 24 hours I've hit about 15 sites with tutorials and information on passing the A+ cert exam. I completely forgot about the CCNA.
Hopefully I can find those books somewhere on the internet, because I am even more broke than a blonde joke.
What other certs would anyone recommend? I just want to add some credibility to my resume.
Thanks in advance.
You're nothing; like me.
I have a previous comment up above that basically labels certifications as a foot in the door, not as a means to an end (i.e., they don't guarantee employment) and I stand by that assertation.
:)
That said, if you want your resume to actually be looked at for a networking position, having the CCNA is not a mark against you. That foot in the door can be a huge, huge benefit - it's your primary means of self-marketing until you either..
1) Learn to write a really effective resume, or
2) Have sufficient experience to get hired on that basis instead.
The CCNA is the key that opens the door to certain kinds of networking interviews. If you're thinking about going for it, consider what kinds of jobs it'll open you up for: Networking Jobs. An awful lot of kids I went to school with years back swore up and down they wanted to be network engineers when what they really wanted to be were sysadmins; the fields are different, the credentials and criteria are different, and the certs you need to support them are different.
The CCNA is what you'll want if you enjoy swimming in Cisco equipment, love configuring VPNs, enjoy troubleshooting RADIUS logging on your AAA box, and suchlike. If those aren't your hobbies, re-evaluate what it is you're really going for.
I passed exam 640-801 in one try, with no real networking experience and having taken no classes.
And we're worried about tech jobs being sent to India...
For all you who are bemoaning the CCNA as a "paper cert," I'm going to point out what is apparently an oft-overlooked fact: CCNA stands for Cisco Certified Network /Associate./ It's not the CCNP (Professional) or CCIE (Internetwork Expert.) Yes, the exam is easy; of course, it's easy to pass on the first try with a little bit of studying. However, you still have to know a few basic things going into the exam to pass it: you have to have a basic understanding of how IP internetworks function, a rough concept of how a few routing protocols work, and the appropriate commands to use on a Cisco router to configure common types of network interfaces. That's all they're trying to assess your ability to do. You don't look for a CCNA if you need a network architect; you hire a CCNA to help configure a
network that someone else has designed. Some companies will undoubtedly misunderstand this, hire a CCNA, and feel misled when they get someone who knows how to type "interface ethernet0/0, ip address 192.168.1.1 255.255.255.0, no shut," but the failure is on their end -- they did not look into what the certification covers. It's all there on Cisco's webpage.
Ahem. Nairobi is the capital of Kenya. Perhaps the poster should read his Encyclopedia Britannica.
Or at least give the World Factbook or WikiPedia a quick look.
If you want to get a CCNA, just read the book by Todd Lammle. When I went to study for it last year, everyone in my group recommended Lammle, and guess what? It's good. Very good.
This is the same thing that happens with most testing in secondary grades. The students memorize just enough of the material to pass the test.
... and then get you to the certification, leaving you to figure out the last part on your own.
:) Cram studying does not lead to long term information retention. How much Calculus do you recall, after years of not actually using it?
Bingo - that's it, the problem, the head of the nail that we're hitting (as it were).
The reason that certifications have lost so much ground in the last five to ten and the reason that nobody respects MCSEs any longer is because of the nature of the testing. When certification exams are a matter of cramming your mind full of administrivia and memorizing cheat-sheets that teach the quick powers-of-two needed to compute a subnet mask, it's no wonder that the average level of the passing applicant falls. Facts and Figures can be memorized with some ease.
MCSE exams fell prey to an entire cottage industry that exists to help people pass them. Think of every radio ad you've ever heard promising that wealth, riches, and beautiful women can all be yours if you just step into the magical and happy world of Information Technology! The industry's job is to ram you through a bootcamp training session and then have you dump that information back out on a certification exam, automagically, while your brain is still raw and bleeding. How much you retain isn't important to them at all; they try to drill into you the erroneous concept that Certification == Job
The brain dump sites online, the exam cram book writers, and the people promising instant results can actually deliver: it is totally possible to ace a certification by studying old tests, reading old questions, and overloading for the purpose of passing your exam.
And, just like back in college, you will not remember most of this information after the fact.
The only way to really prove yourself is to start small, to learn what you can, and to etch it into your mind through repetition and hands-on experience.
Do what you have to to get your certification. Do not expect to land an 80k/yr job off of it alone -- it won't work. (God help you if it does, you'll learn what being fired feels like very shortly thereafter.) Expect to land a starter job, and use that to make an impression on your bosses; learn fast, learn often, be a good employee.
The recommendations of people you've worked for and with will serve you better in the long run than your certification will. It's time to rely on your qualities, rather than the qualities the paper says you have.
Yeah, that about covers it.
In my case I started this at home. Got the "addiction" and started buying and tinkering with computers as fast as my budget would allow. I used to be the guy who bought new games and secretly hoped something wouldn't work right out of the box so I could figure out why. One day I looked up and I knew enough that someone would actually pay me to fix PCs for a living.
Eventually that led me to better technician jobs and finally the desire to work on bigger problems. I got an entry level position here where I still work and started learning networks from my boss (And he started his "addiction" in the early 70's). At one point about four years ago management decided that we all needed to be MCSE certified and laid out a bunch of money to a training company for classes and vouchers. We were running Novell then and since we had been given the "We're switching to NT now" speech (again from management) they felt like we needed some training.
We were all like "Ok, whatever." I went to the first class and tried to get into it but I wasn't learning anything. Sure I was learning how much Microsoft thought of their product but everything relevant was stuff I learned on the job. I ended up passing on the rest of the classes and just picking up some "Dummies" books and finishing it on my own.
The vouchers my company paid for were of some use (because I wouldn't have bothered to pay for those tests on my own) and we ended up using the class time for another employee who needed some SQL training but the content was worthless. It amounted to me spending time learning enough "Administrivia" as you so nicely put it just to pass a stupid test I didn't really need and didn't want in the first place.
On the other hand my brother jumped into this field because you could make bank in it. He went to college, I didn't. He has a CIS (or one of those, I don't really know or care much) degree and as soon as he got out he went through the Certification feeding frenzy and jumped into a job from the get go that paid more than I was making. I tried to talk him into spending some time to learn a foundation but he wanted the money and he got it. The thing is though he's lost and in way over his head. I think it's only a matter of time before he's looking for work because he doesn't love this stuff and he doesn't know it well enough. His paper means not much in the long run.
It might sound like I'm looking forward to him hitting the wall but I'm not. I really just wish he'd listened to me (and had gone after something he enjoyed instead of what he thought was going to get him in a BMW faster). I've seen enough of the paper admins to know that no good comes of it.
Appended to the end of comments you post. 120 chars.