Network Warrior 228
Fatty writes "Entry level certifications such as the Cisco Certified Network Associate (CCNA) have become the source of many jokes to people in the industry, largely because of the seemingly inept people that proudly display their certifications. This is made worse by the volume of books geared only to get people through the exam. Network Warrior bills itself as the exact opposite — if the subtitle is to be believed it contains "Everything You Need to Know That Wasn't on the CCNA Exam". With everything from the architecture of the 6500 to layers 8 and 9 of the OSI model (politics and money), it does a pretty good job." Read below for the rest of Sean's views on this book.
| Network Warrior: Everything You Need to Know That Wasn't on the CCNA Exam | |
| author | Gary A. Donahue |
| pages | 598 |
| publisher | O'Reilly |
| rating | 9 |
| reviewer | Sean Walberg |
| ISBN | 9780596101510 |
| summary | A practical look at what you really need to know to run a Cisco network |
The CCNA exam is supposed to test a candidate's understanding of networking fundamentals. Over the years it has expanded to include more advanced material, and now covers networking theory, switching (including spanning tree and VLANs), and some of the intermediate routing protocols such as EIGRP and OSPF. Despite the breadth of content the exam doesn't (and can't) cover things that many network folk take for granted, even things like what the "demarc" is (short for demarcation point, the the place where the carrier's responsibility ends and yours begins). While the exam's topic list is broad, the level of detail is shallow in most places. Someone may study spanning tree enough for the exam, but have no clue where to place their root bridge when they get into the real world.
It is for this reason that I found Network Warrior to be helpful. It's goal is to point out both the technical areas in which the CCNA falls short, and to teach the reader the non-Cisco aspects of running a network.
Technically I found this book quite sound. There were a few things one might disagree with but nothing that detracted from the rest of the book. In several spots the author was keen to point out behaviors that deviated from the documents, such as in Quality of Service (QoS) and in upgrading certain modules in the 6500 chassis. He also illustrated where the theoretical concepts on network design fall short in the real world.
Routing and switching takes up the first third of the book. The switching section is largely a review of the CCNA material with some notable exceptions. First and foremost is a chapter exclusively on autonegotiation. The CCNA exam may only discuss how to set a port to a fixed speed, but anyone who has worked with a network for more than a few weeks will have run into a speed or duplex mismatch. This chapter explains some of the history behind Ethernet and its relevance to autonegotiation, explains how it works, how it fails, and how to recognize the problem, and finally offers advice on when and where to use autonegotiation.
The second major deviation from the CCNA switching syllabus is in depth coverage of Etherchannel and spanning tree (STP) Both of these protocols are integral parts of network design and operation, but the exam barely touches Etherchannel and doesn't get into the complexities of spanning tree (though this changes with each iteration of the exam.) Network Warrior provides techniques and a demonstration of finding a layer 2 loop. Surprisingly though, there is only mention of standard 802.1d legacy spanning tree and some Cisco extensions such as Per VLAN STP and backbone fast, and no mention of the newer standardized enhancements of 802.1s/w (rapid spanning tree and multiple spanning tree) which have been in common use and have been put on the latest version of the exam (released after this book went to press)
The third deviation is the inclusion of CatOS commands instead of just IOS like the exam. As the author repeatedly points out, CatOS is in use on many 6500 chassis and is still in active development, so there is no reason not to know it. This theme continues throughout the book whenever the 6500 is used as an example, which is often.
The routing chapters are full of new material. The sections on the routing protocols themselves are short and don't add much beyond what the CCNA certification teaches. Redistribution and route-maps, however, are well explained. These two technologies which can be used separately or together can be found on almost any network and are very complex. I thought these sections were well done, as they gave enough details to be practical without getting down into all the different scenarios. Tunnels make an appearance in these chapters, which themselves aren't very complex, but aren't a part of the CCNA blueprint.
At this point, roughly page 180 of 550, the rest of the material isn't found in the CCNA blueprint.
Part 3 of the book is all about multilayer switching, specifically the 3750 and 6500 platforms. In particular the description of the 6500 architecture is much more succinct that can be found by searching on Cisco.com. There is an in depth explanation of how the various backplanes on the chassis works, which leads to an explanation of how to determine which cards are slowing down your switch.
I think the hidden gem of the book is part 4, though, which is all about telecom. In these chapters are an explanation of how carriers operate and how to speak the lingo of telecom techs. Even though networks are moving to Ethernet based services, traditional DS1, DS3, ATM, and frame-relay networks are still commonplace. The book has a solid explanation of how TDM based circuits actually work, the various options available to you, and how to properly order and troubleshoot them. I think back to when I was getting started in this field, and dealing with carriers was difficult.
Quality of Service, the features that let you guarantee and limit bandwidth to different types of traffic, have a section in this book too. The book largely focuses on the simple weighted-fair queuing (WFQ) and the current class-based WFQ with low latency queuing for voice. Configuration instructions can be found on Cisco's site easily enough, but Network Warrior delves into some of the behavioral aspects the documents shy away from such as when the queuing mechanisms actually get used. There is also a solid look at how to make sure the QoS is working as intended.
In the middle of all of this are chapters on the firewall and load balancing modules for the 6500, the PIX firewall, and IOS based load balancing. For someone with an ecommerce slant these might prove helpful, but given that these topics are books in themselves, it's hard to do them justice in a few chapters.
The last part of the book is on network design, which encompasses not only the steps needed to build a network, but also planning IP address allocations and how to pitch your ideas to management. Again, the book is not trying to be the definitive text on the subject, but it manages to impart a few words of wisdom, especially the so-called "GAD's Maxims", and "How not to be a computer jerk".
Well thought out examples were plentiful, along with anecdotes from the author, usually showing the consequences of doing things wrong. The illustrations did a great job of conveying the point at hand. Even though I've been doing this stuff for a while I learned several time saving techniques that I've already been able to put to use.
This is a great book for people just getting into the industry, with their CCNA or without. It offers practical advice rather than dry textbook like explanations which is a welcome change. Even those with a few years of experience under their belt will be happy reading through Network Warrior.
Sean Walberg is a network engineer and author living in Winnipeg, Canada.
You can purchase Network Warrior from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Re:What value DO the entry level certs have? (Score:1, Informative)
On the other side of the coin, is that a cert does provide "proof" that a certain level of knowledge was acquired (I say was, because it only proves you had it when you took the test). Now, a lot of larger companies won't hire someone unless they have either a bunch of verifiable experience (5+ years at a reputable company), or a cert.
So is a cert good for something, yes. Is it deserving of all the importance that people give it? Well, that one I leave for you to decide...
Re:Interview Questions (Score:4, Informative)
I'd almost buy that, but for a local vocational school that is notorious for "You pay, you pass" assembly-line certs. A guy that we tried out was a card-carrying CompTIA A+-certified tech. To help test him {having had experience with this school's graduates before..} I took him to an open PC on the bench and asked him to point at the motherboard.
He pointed at the case.
I told him, no, not the case, the *motherboard*.
He blinked twice, and pointed at the case again. He didn't last the day.
IMHO, those little pieces of paper don't guarantee jack anymore. -sigh-Re:What's with the militant terminology? (Score:3, Informative)
Read the book and Cisco IOS Cookbook, my two cents (Score:3, Informative)
How to place this book is like this, so you've finished or are close to your CCNA and would like some sound practical advice to round out the course or maybe to help you revise it, well this is the book for you. If you know more and are in deeper Cisco terrority well you might like this but you'd probably prefer the Cisco IOS cookbook.
Off topic - I also got a copy of Limoncelli et al's revised version of The Practise of System and Network Administration in the same batch, given the first edition was most excellent there is little to say except the second is even better. Common sense and practical knowledge without getting lost in OS or application issues.
I disagree... (Score:5, Informative)
My point is had I actually studied for a CCNA before I was hired, I would've hit the ground running most likely would've advanced to my NOC position in 3 - 4 months less time. The CCNA is not a joke. It may not teach you ALL the terminology and EVERYTHING you need to know about EVERYTHING, but it's a hell of a good start.
Re:Interview Questions (Score:2, Informative)
Distinguish CCNA from A+ (Score:5, Informative)
The A+ exam is a complete joke. It might have been relevant 10 years ago, but isn't anymore. The vast majority of questions were completely irrelevant today, and mostly irrelevant for any computer faster than 500MHz. Most of it was pure memorization, the kind all those cram books are for. There were very few real-world questions -- less than a half-dozen. There were even a few questions that were nonsense -- none of the answers were applicable, much less valid, and in some cases the question didn't even make sense.
The CCNA, however, is a killer. I took mine in May 2007. The first part of the exam is roughly one-third memorization questions, one-third diagram interpretation questions, and one-third real-world questions. Most of the diagram questions are trick questions with multiple realistic-looking answers. (In other words, you can't just look for the "obvious" answer.) This part of the exam is meant to test your grasp of networking concepts.
The second part of the CCNA exam is what really gets you, though. It's all about configuration. Most of it is spent in a simulator. And not just a simulator for one router or switch, but a simulator for an entire network. One of my questions involved configuring 4 different routers and 3 switches. Oh, and they can disable parts of the simulator to make your job harder -- like having to diagnose a connectivity problem without being able to ping or traceroute. And yeah, they like to throw multiple IOS versions at you to make sure you know the different variations of the commands (especially for switches). You cannot cram for these simulator-type problems.
I tend to consider myself a pretty smart guy. I've been working as a network admin for 10+ years, albeit not with Cisco equipment. I aced the classwork for the CCNA courses without putting forth any effort whatsoever. I did homework in class and never had to come in after hours to catch up. And yet, I had ~45 seconds left on the timer when I finished part 2 of the CCNA exam. It's that tough, and they've got it timed down to the last minute. You do not have time to flounder and guess.
If you don't know your stuff backwards and forwards, you are not going to pass the second half of the CCNA exam. It's that simple.
Now, having said all of that, remember: the CCNA is the entry-level exam. It's not meant to certify that you can walk into a company and rewire an international infrastructure by hand. It's meant to certify that if you put me in front of a router or a switch or a small network that is having problems, I can most likely figure out what the problem is. The building-huge-networks stuff is part of the CCNP, not the CCNA. (The first CCNP class is, after all, "Building Scalable Networks".)
I see plenty of haterade about the CCNA exam, but I never seem to see it from people that have taken the tests. And I have to wonder: for all of those exam-crammers with CCNAs that everyone seems to know, when did they get their certs and are they current? I doubt it.
Re: OSI? Do you mean TCP/IP? ;-) (Score:2, Informative)
All People Seem To Need Data Processing =
A)pplication 7
P)resentation 6
S)ession 5
T)ransport 4
N)etwork 3
D)ata-Link 2
P)hysical 1
Now do I get a gold star?