//Why you want to specify the channel ?  Once you create a SSID is up to the Client and the Access Point to negotiate the channel.//   Thanks Flavio for the response.  What you are saying is absolutely correct, however I am running into an issue that my Access Points are failing to detect honeypot on UNII-3 channels only while It detects it well on all other channels.  ... View more

Thanks Hayden for your response.    However the 4800 AP has actually 4 radios in them. 5GHz Dedicated Radio XOR Radio (2.4/ 5GHz Client Serving) Third radio for the AP to perform analytics, Hyperlocation, and WSM (WIPS and WIDS) BLE radio Now the question is whether the third radio is capable for performing Analytics, Hyperlocation and WSM simultaneously?  ... View more

Thank you Andrews for your response. Please find below my responses inline:   I see no issues, I have had WLCs connected to 3 different CMX servers to beta test CMX versions. My setup was 8540s with 6000+ APs, 40k concurrent clients and about 100k probing clients at any one time, to give you a load perspective. It was CMX that struggled, not the WLC Adnan: Were all the CMX servers running different CMX application or they all running the same cmx application (location)? I my case its CMX for Location plus CMX for presence with the same WLC having its NMSP subscribed to it.   That being said there is an issue (not sure if they every fixed it) where you could only do hyper location to a single CMX instance.  Adnan: This is going to my second major concern. In your deployment you were able to do hyperlocation with only single CMX server? The problem is my network too is going to scale beyond 5000 APs and one instance of CMX can support only 1000 APs. Based on your experience we can have only one to one mapping between hyperlocation enabled CMX and WLC? There's separate thread that I am running on similar concern, however did not got any leads though: https://community.cisco.com/t5/wireless-and-mobility/mse-3375-for-hyperlocation-how-to-increase-scalability-for-max/td-p/3773482     I do need to ask any reason for a location and presence box? you can do nearly everything using CMX location that you can do in the presence box.   Adnan: Its correct that CMX-Location does almost every thing that CMX-presence does. However CMX-location do have some scalability issues. So we are first running the POC to capture all the limitations and then setting the right expectations from the product. We may even eventually end up having both (CMX-Location & CMX-Presence) in long run. ... View more

Hi Leo,   Thanks for the response.    However WLC does interacts directly with CMX through NMSP for transmitting aggregated RSSI and wIPS information.  ... View more

Thank you Patoberli for hinting out the problem that I am most likely hitting.    My note 8 was running on Android 8.0 while Note 4 was running with previous versions of Android. Appears IOS started mac randomization feature back in 2014 (IOS 8). Could not find how exactly mac randomization is facilitated in Andriod,  in IOS it however happens every 30 minutes (default parameters) MAC Randomization for Android Android requires the MAC address of the Wi-Fi Aware discovery (NMI) and data interfaces (NDPs) to be randomized and not be identical to the true MAC address of the device. The MAC addresses must be: Randomized whenever Wi-Fi Aware is enabled or re-enabled. When Wi-Fi Aware is enabled, the MAC address must be randomized at a regular interval configured by the   NanConfigRequest.macAddressRandomizationIntervalSec   HIDL parameter. This is configured by the framework by default to be 30 minutes. Note:  Per the Wi-Fi Aware spec, randomization may be suspended while an NDP is configured. Study of MAC Address Randomization Apple iOS 8 and MAC Randomization and its impact on (CMX) Solution   ... View more

The problem goes as this:   The network is comprised of over 250 APs. The hyperlocation is disabled globally and enabled on an AP group of an auditorium which has over 10 APs. The CMX is just uploaded with just 1 map comprising of these 10 APs.   1. The moment any user device comes into the auditorium and associates with auditorium AP, the user entry under "Associated clients" increments. (As expected). However when the user device moves outside the auditorium and connects on to the other APs outside the auditorium, the "Associated clients" entry does not decrement.   Ideally it should be the case that when a user device moves outside the auditorium and connects on to the other APs which are not yet placed on map added on CMX, then the "Associated clients" counter should decrement (following the age out time for client- default being 10 minutes)   Please let me know if I am missing on something here. ... View more

I again started seeing back the same issue. After restarting the cmx services, the "probing only clients" starts reflecting for a while and then again their counter remain at 0 most of the times. ... View more

The maximum length of Antenna cable offered from Cisco for N(m) R(f) is 20 Feet. If longer antenna cable lengths (exceeding 20 meters) is still the requirement, then the below combination could be opted in. /AP-1572(N-Female) <----> (N-Male)AIR-ACC370-NM-RF=  (R-Female)<-----> (R-male)AIR-CAB050LL-R (R-female)<-----> (R-male) ANT-2544//   Since RP-TNC ports looks different from the name they carry, have included their pics as well.        ... View more

Have started seeing back the probing clients without being making any changes of CMX.   However after running into similar issue, the option that has to be checked into is the settings of Filtering Parameters.  There's an explicit option of "Exclude Probing Only clients"   ... View more

Appears from CMX-10.3.1-35, the names are ammended to be more meaningful. "Connected" being changed to "Associated" "Detected" being changed to "Probing only"   The new names in actual makes more sense. ... View more