Effective this month, Cisco diverged the code versions and created a separate version of code to run MESH only. What this means in a nutshell is that you must use one controller to run MESH and one to run indoor APs. You can still use the older versions of code to continue to support 1510s and indoor APs but you will not receive support from Cisco. The "train" as it is called was separated due to MESH development slowing down the internal AP code development. The official marketing line is that this will allow for quicker development of new features for the 1520 series MESH APs. The train is scheduled to remerge in 12-18 months so that once again you could use one controller to manage both indoor and outdoor APs. Don't hold your breath on that one. In either case, you still manage both indoor and outdoor controllers from a common version of WCS. I hope that answers your question.
Not quite... Indoor APs are fully supported currently in the "mesh" release train, but the feature functionality for indoor, non-mesh APs is currently based on the 4.1.x release.
We have released the 4.2.x code for indoor APs a week or so ago, so there is some feature functionality not yet available in the Mesh release. We will sync functionality again in the future. Check with your Cisco account reps for the details.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...