CCNP Ont Official Exam Certification Guide [With CDROM]

I received the book 'CCNP ONT Official Exam Certification Guide" in very good condition. The book is interesting to read makes the concepts quite easy to understand. I recommend the book to anyone who wants a better understanding of Quality of Service mechanisms.

This is one of the few Exam Certification Guides I'd say is enough to pass with, if it's the only thing you have to study with. It does a very good job of covering the exam. There are times (Chapter 7 in particular) where I wanted to strangle the author, as he kept repeating the same things. The book is very thin compared to the other CCNP Official Exam Cert guides, so there may have been some padding involved. Regardless, the box is a good solid core. Combine it with some good test prep software like Transcender, and you should easily pass ONT

Minimal Fluff. Clear and concise explanations, very good examples. I used the book to study for the ONT exam, which I successfully completed. There are a few methods that are covered and all I was interested in was, what the methods are, why were they developed, when to use them and how. The book proved to be right on the money. I would recommend this book as a Reference source as well. Personally, I wish they would write technical books in this fashion using the following headings: Method, Why developed/Issues addressed, When to use and How. Just forget all the fluff and get down to the Nitty Gritty.

Queues baby. That's what it's all about. First of all, consider the VoIP scene. You ain't getting no guaranteed action over that converged network unless you're doing some low latency queuing (with is class based weighted fair queuing + a priority queue) and probably some compression on that real time protocol (RTP) header. Then there's the fact that VoIP has to interact with the plain old telephone service (POTS) and the gateways, gatekeepers, FXO, FXS, earth and magneto trunks, all that needs to be adapting the packets to the analog signal domains. No way you're getting by without it. And then there's the per-hop DiffServ with its many and varied ways of prioritizing. Software queues, hardware FIFOs. Shaping and policing, dropping and buffering, ingress and egress, oy it makes my head hurt. But you need to be aware of the tools. Alternatively, signal the whole thing with IntServ (RSVP) but don't expect it to scale as well. The whole question of policy at the edge comes up again here, and while the conventional wisdom is don't be breaking open packets in the core, the bottom line is that you don't always want to send a guaranteed service into a cloud and hope for the best on the other side. QoS knobs have been so many and varied over the years that it's good there are finally some macro-based to set them up with templates. The modular QoS CLI and AutoQoS are two hopeful examples of simplifying the IT workday, and the Security and Device Manager (SDM) GUI is another nice try. Of course, a little tuning after the wizards have painted with their broad brush tends to help you get things right. And let's not make too many assumptions about wires. Who doesn't have a laptop nowadays? And the wonderful things about standards is that there are so many of them, and that's just counting the ones that begin with 802.11. Encryption, authentication, authorization, rogue access points....you can bet that security is the killer app for wireless. And by the way, this book maps pretty nicely to the test, and if you understand it you have a very good shot at passing that bad boy.