Network Warrior: Everything you need to know that wasn't on the CCNA exam at Dominant Systems Book Store

Everything you need to know that wasn't on the CCNA exam --This text refers to an alternate Paperback edition.

Customer Reviews & Comments
Network Warrior is the best network administration book I've ever read. I spend most of my reading time on security books, but because I lean towards network security I like reading complementary sources on protocols and infrastructure. Gary Donahue has written a wonderful book that I highly recommend for anyone who administers, supports, or interacts with networks. Network Warrior may be the best book I will read in 2007. Why is Network Warrior so great? I think the key is the author's willingness to share personal recommendations. There are plenty of books about technology and syntax. I've read and reviewed many, most of which I liked for what they offered. However, it's rare to read a network book that says "here's how you should implement this," rather than just list options. I'm at the point in my career where I know what I might do; now I want to know what a real expert would do. Donahue provides that wisdom in many sections, but especially in Part VIII on network design. A second reason I really enjoyed Network Warrior was its coverage of a variety of Cisco features. Sure, I had read of many of these elsewhere, but I thought Donahue made many of them clear, especially in comparison to each other. There are better references for ACLs, like Cisco Router Firewall Security by Richard Deal, but when ACLs are described next to route maps or VLAN maps, Ciscoland becomes a little easier to understand. Donahue's explanations of EtherChannel, switching algorithms, and autonegotiation are other good examples. I even admit that the author corrected my misunderstanding of QoS, as he says "QoS does not limit bandwidth, it guarantees it, which is not the same thing" (p 429). Elsewhere he says "When there is no congestion, any protocol can use any amount of available bandwidth it needs" (p 428) and "while scheduling of packets always takes places, the limits set are really only enforced during congestion" (p 427). The third reason I like Network Warrior is the attention paid to understanding the fundamentals of certain technologies and products. The author ensures the reader gets a real grounding in telecom terms and technology, like T-1 lines. For products, I liked chapters on the 6500 series switch, content switches, and layer 3 switches. Finally, the writing is exceptionally clear. The diagrams are excellent and make their point very well. The author's suggestions for being a better administrator apply to any technical operator. I liked Donahue's repeated suggestion to "never assume anything" and to start troubleshooting at layer 1. Although I rated Network Warrior five stars, in a second edition I would like to see more on layer two fundamentals. I would also like to read about 802.1X and perhaps even Cisco NAC, since it seems to be becoming popular. Overall, however, you should buy and read Network Warrior right now. I loved it and will recommend it to anyone who wants to be a better network administrator.

Back To Top