Deploying and Troubleshooting Cisco Wireless LAN Controllers
Posted: February 1, 2010 at 4:23 am | Tags: cisco, controllers, Deploying, troubleshooting, wireless

Product Description
This is the only complete, all-in-one guide to deploying, running, and troubleshooting wireless networks with Cisco® Wireless LAN Controllers (WLCs) and Lightweight Access Point Protocol (LWAPP)/Control and Provisioning of Wireless Access Points (CAPWAP). Authored by two of the most experienced Cisco wireless support professionals, the book presents start-to-finish coverage of implementing WLCs in existing wired and wireless network environments, troubleshoot… More >>
Deploying and Troubleshooting Cisco Wireless LAN Controllers
The Discussion
see what everyone is saying
interesting and detailed book where you can read and also find out the tracing done in the WLAN LWAPP/CAPWAP protocols and their features
Rating: 5 / 5
Over the past year I have been studying/working towards my CCIE Wireless so I have read a lot of the different books out there and this is by far the best book out there. That being said of course there are not that many options to begin with, other than plenty of white papers and highly technical Cisco docs. This book is a very easy and quick read for anyone having worked with the Cisco Unified Wireless equipment. I’ve found myself on a few instances opening up the book to refresh myself on certain configuration examples when running into issues.
I passed my CCIE Written before this book was published but have used it as a study guide for the CCNP-Wireless which I have one exam left. Without breaking the NDA rules I can say this is a great study material for all the certification series. While the CCNA Wireless book is a great intro I find this book more relevant and in depth to the test blueprints and will help you pass the exams.
Now if we could just get a CCIE-Wireless Lab Guide to study off of I’d be all set!
Rating: 5 / 5
The first chapter is the most valuable. It offers broad tips for a top down debugging approach to a wireless network problem. Also, it is largely independent of specific hardware elements. You can apply the guidelines even if you have non-Cisco items in the network. Of its advice, two very good tips stand out. The first is simply to have an extensive and complete network diagram. Do this when everything is [presumably] working. Don’t wait till things go wrong before amassing such a diagram.
The second tip is to imagine you are offsite and are talking on the phone to an onsite sysadmin. And no visuals on your phone. It’s strictly audio. This gedanken forces you to focus on what might be the key features of the problem.
The rest of the book then delves into specific abilities of Cisco boxes. Often there might be diagnostic text output that you can get. Cisco has been careful about enabling its machines to provide copious diagnostic dumps. The mass of detail is needed because of the many possible failure symptoms. But this also means that part of the skill you should cultivate is an intuition about what to look for in a potential surfeit of a data dump.
One impression from the book is that wireless problems can be harder than those in an all-wired network. For the latter, at least in principle, you can trace the wires and test each link. But wireless transceivers can overlap in broadcast range. While evesdropping does not require physical access to your equipment by an adversary.
Rating: 4 / 5