• Cisco Prime version 3.0 or higher— The function of this software is to correctly place the Access Points on a map and describe the orientation of the Antenna. Exporting maps to CMX 10.2.x

• Cisco CMX 10.2.1 or higher— The function of this software is to receive the information from the Hyperlocation module and antennas and then calculate the location. Furthermore, it provides this location via a display on a map of client locations and an API with the calculated location. The L-AD-LS-1AP-N – CMX Advanced License for 1 AP is required.

• Cisco Unified controller 8.1(MR3) or higher— The function of this software is to support the new hardware and provide a tunnel for the information from the WSM to get to the CMX 10.2.1 server

• In addition to these components, you will also need an NTP server (application or router running on same subnet) as you will need to configure the controller to sync with an NTP server through the Hyperlocation settings. You will also need to configure a gateway on the switch and controller.

• Suitable Cisco controller such as 2500, 5508, 5520 etc. running 8.1(MR3) or higher

• AP-3600 or AP-3700 These are the current Cisco Access Points supporting Hyperlocation modularity

• AIR-RM3010L-x-K9= Hyperlocation Module with Advanced Security

• AIR-ANT-LOC-01= Hyperlocation Circular Antenna

• Wireless clients (tablets, smartphones and so on)

Figure 1. Modular Components for Hyperlocation

Hyperlocation is a combination of a new Hyperlocation module with Advanced Security that replaces the older WSSI/WSM: AIR-RM3000M module which does not support Hyperlocation as it lacks the ability to support an advanced Hyperlocation antenna system.

• Advanced WSM support (as a stand-alone module) similar to the older WSM but with 802.11 20,40 and 80 MHz support (non-serving radio)

• Advanced WSM & location when used with the Hyperlocation antenna

• FastLocate support (non-serving radio)

• Integrated Bluetooth Low Energy “BLE” Beacon transmit capability.

The Hyperlocation methodology of calculating location using Angle of Arrival (AoA) tracks 802.11 OFDM clients (meaning 802.11a/g/n/ac clients) that are associated (connected) on the network and is able to do so with much higher accuracy than conventional Real Time Location Systems (RTLS) that rely on only RSSI (RF Signal Strength).

The final calculation of location not only utilizes Cisco's AoA method but also takes into account many other factors including RSSI for a very accurate location assessment.

Note	AoA Hyperlocation (at this time) does not track “pure” 802.11b clients as AoA works best with OFDM emissions meaning 802.11a/g/n/ac associated clients so 802.11b clients will be tracked using conventional RSSI data.

Hyperlocation is not designed (in this software release) to track passive/active (non-WiFi) RFID tags or Bluetooth Low Energy “BLE” beacons, or non-associated clients with Hyperlocation accuracy.

Note	While the hardware is capable of tracking such devices, these features using Hyperlocation high precision accuracy are not available today in software and are being considered in subsequent releases.

Hyperlocation provides a distinct increase in location calculation capabilities, (as shown in Figure 2 below) increases in location accuracy with the bottom curve on the chart is a Cumulative Error Distribution Function (CDF) based on calculating location using the standard RSSI method and the top curve is the CDF function of a location calculated using Hyperlocation technology. The difference between the two curves is the increase in accuracy you get by using Hyperlocation technology.

Figure 2. Increases in Location Accuracy with Hyperlocation

The Hardware SKUs that are required for Hyperlocation are:

• Hyperlocation with Advanced Security Module—Cisco P/N AIR-RM3010L-x-K9

• Hyperlocation antenna array—Cisco P/N AIR-ANT-LOC-01=

These are shown in Figure 1

The Hyperlocation (Circular Antenna Array) is a 32-element antenna design that provides 360-degree coverage around the Access Point. It is designed to integrate into the Hyperlocation module with Advanced Security providing precise RF Angle of Arrival (AoA) information allowing the embedded software the data required to calculate location using a more granular approach.

The antenna array and Hyperlocation Module with Advanced Security integrate into the Cisco 3600 and 3700 Series Access Points using the module option allowing both module antennas (center) and Hyperlocation circular array (outside) example below is an AP-3700.

If you could take the cover off the product, here is how it would break down (module in middle) antenna array around the AP. All of the antennas (around the AP) determine precise location.

Figure 3. WSM w/Advance Security and Hyperlocation Circular Antenna (a look at the antenna systems)

Hyperlocation Module with Advanced Security features and caveats include:

• No requirement to deploying a separate and dedicated overlay of AP’s in monitor mode for full spectrum monitoring

  Eliminates the need for an extra cable pull and additional infrastructure costs Module draws its power from the Access Point

• A field-upgradable 3rd Radio module add-on to the AP3600 and AP3700 Series APs Dedicated 2.4 GHz and 5 GHz radio—both bands supported in a single module.

• No configuration required—module automatically scans all channels on both bands Independent integrated antennas within the module 3 Tx antennas x 3 Rx antennas Additional antenna and radio for Bluetooth beacon functionality

• Enables 3600 & 3700 Series Access Points to be the only AP to concurrently:

  Serve clients on 2.4 and 5 GHz—with internal integrated radios and antennas 4x4:3

  Perform wIDS/wIPS security scanning on both 2.4 and 5 GHz bands all channels

  Perform CleanAir spectrum analysis on both 2.4 and 5 GHz bands on all channels

• Offloads CleanAir monitoring and WIDS/WIPS Security capabilities to the Monitor Module CleanAir, wIDS/wIPS, Context-ware location, Rogue Detection and RRM

  Always on full spectrum analysis, on all channels for both 2.4 and 5 GHz bands.

• Hyperlocation with Advanced Security Module can be purchased with or without the Hyperlocation antenna array.

  Customers will be able to field upgrade existing 3600 and 3700 APs with WSM or WSM +Hyperlocation

• No configuration is required - easy field upgrade customers simply:

  Install the Wireless Security Module or WSM + HYPERLOCATION into the bottom of the Access point (see figure 1) Power on the AP and all the Monitoring and Security capabilities will automatically be offloaded to the Monitor Module

Power down the 3600 or 3700 Series AP.

1. In this release, we have a limitation on 1 x WLC to 1 x CMX 10.2.x. Right now no other CMX or MSE system should be assigned to the same WLC during your testing or it may impact AoA. Any given controller can only talk to a single CMX 10.2.x system running AoA. (A second non-Hyperlocation CMX 10.x system can be added, but ensure that this system NEVER has Hyperlocation feature enabled).

2. Install the Hyperlocation Access Points; try to keep the spacing between 30 to 70 ft (maximum) apart. Ideally 50 ft. apart is recommended (make sure to document your spacing) – Bring them in closer if you have lots of walls, clutter etc. 50-60 ft or closer is best to get AoA locations calculated. When the AP is much further away from the client there is more likelihood that the client will not be located via Hyperlocation.

3. Installation should be done using AIR-AP-BRACKET-2 which should be supplied with the module. Bracket1 and Bracket-3 (in-tile bracket) are not designed to be used with the HYPERLOCATION array.

4. A general rule of thumb is to have 3 or 4 access points that are within line of sight of the device at a distance of less than 70 feet. (Please note, if you are conducting this test in Meters, please make sure to translate all numbers, the CMX 10.2.x software only supports display of the X,Y location of clients in feet.

   Note	1m = 3.28 ft.

Some basic guidelines on Site Surveys/deployments…

• Survey or try to maintain consistent -65 dBm RSSI for data, voice, video, location

• 10 to 20% cell overlap for optimized roaming and location calculations

• A good rule of thumb is 1 Access Point per 2,500 square feet (best performance)

• For high density applications perhaps add an additional AP in the middle.

Note	Provide spacing during the installation for better accuracy and add one in the middle.

Figure 6. Note Spacing during Installation - avoid metal obstructions near the AP antennas

Note	Spacing during Installation - avoid metal obstructions near the AP antennas

Figure 7. AIR-BRACKET-3 is not compatible with Hyperlocation Antenna AIR-ANT-LOC-01=

AIR-BRACKET-3 is not compatible with Hyperlocation Antenna AIR-ANT-LOC-01= AIR-BRACKET-3 is not supported due to the mechanicals of the Hyperlocation Antenna Array and the requirement for a precise Azimuth location.

Note	It may be used when only the Hyperlocation Module is used for Security and FastLocate.

Figure 8. Avoid mounting the Hyperlocation AP above the ceiling tiles

With Hyperlocation, it is essential that the EXACT location of an AP be recorded and correctly entered into Prime Infrastructure (PI). The location needs to be accurate down to several inches. Location error is compounded by location of several AP’s being off, so it is essential that the X-Y and height of the AP in relation to the map in Prime be correct down to 1 inch. In addition, the orientation of the antenna needs to be correctly set in Prime and correct to within 5 degrees.

Please record these four attributes of each AP and double check these before they are entered into PI.

Figure 9. Understanding AP Map Placements in Prime

Now let’s set the AP position on the Prime Map.

Figure 10. Placing the AP on the Prime map

Prime defaults on Azimuth (right=0) (left=180) in this case the AP is pointing with the arrow to the left.

Azimuth gets more complicated when the building map isn’t a “perfect square” this is why it is strongly suggested that the Access Points be installed so they are all aligned facing the same direction.

Figure 11. Placing the AP on the Prime map

Prime defaults on Azimuth (right=0) (left=180) in this case the AP in the top of the picture is pointing left and so 180 is entered in the Azimuth.

Of course the X-Y map can be in other orientations, and in the case of this particular building (only the top of the building) is a “square” so the angle of the left and right sections of the building needs to be determined.

Since ceiling grid rails are most likely the best source of a “true angle” for azimuth, it is recommended that each “group of APs” say all those on the left have their orientation in the same way if possible then once that angle (azimuth) is determined it should remain constant for the other APs in that area. This minimizes user errors as each individual Access Point has its own properties and azimuth adds to the complexity.

Additionally, the orientation angle for the Access Point internal antenna (the antenna servicing clients) its angles should be set to the same as the Hyperlocation antenna.

Figures below shows simply reinforce azimuth angles should be consistent.

Figure 12. Configuring orientation of Internal Antenna

Figure 13. Configuring orientation of Hyperlocation Antenna

A good technique is to use a floor roller to map the distances between access points. This can be used to correct the location of APs on the map. The process would be to fix one AP and then measure the distance to additional Access Points.

These additional Access points can be measured in both the X and Y direction and this offset can be verified to be correct in Prime. This is a manual process but is essential for getting to the +/- 1 Meter accuracy that is possible with this module.

Note	Sometimes it is easier to mark the floor with the location of the Access Point by using a “plumb bob”. This allows the floor roller to measure the location without guessing your position.

Before proceeding with doing location accuracy testing, you should ensure that CMX 10.2 is correctly installed.

A CMX 10.2 Installation/configuration guide is available on CCO, this is a quick overview of the steps required.

• Deploy the Installation OVA using VMWare 5.5 (VMWare versions below that are not supported).

  If VMWare 5.0 is only available, you can install a CMX 10.1 system from CCO and upgrade it to CMX 10.2.x.

• Follow the Installation Guide

  The Installation file to use will have a file name similar to this one (depends on version used) Cisco_CMX-10.2.0-150.ova

  Make sure that the system is designed to use the large-scale CMX 10.2.1 deployments. Specifically 16vCPU, 32Gig RAM and at least 500 Gig HD space.

• Upgrade the Installation immediately to .CMX version 1108.

• Upgrade procedure is in the Installation Guide. Use the GUI based upgrade.

  To setup CMX 10.2.1 to track only associated clients; please make sure that the checkbox "Exclude Probing Clients" is checked as shown:
  

  
  
  

Procedure

Step 1	Verify the APs join the controller, if they do not - then verify date/time is accurate on controller, verify you have the same gateway defined in the controller & switch and they are reachable, also make sure the switch can provide PoE+ (802.3at power) or use local power or AIR-PWR-INJ4 PoE mid-span injector.
Step 2	Again if you have not done so, you will need to configure a gateway on the switch making sure the gateway is reachable from all the ports the APs are connected to.
Step 3	Once the AP has joined the controller you can verify see below. Note    For now you may want to disable the Hyperlocation module if you are going to do location testing initially without the Hyperlocation device. At this point, the AP should be connected to the controller and running without the Hyperlocation with Advanced Security module running.

For a basic overview on location-based services (reference only) see the following URL http:/​/​www.cisco.com/​c/​en/​us/​td/​docs/​solutions/​Enterprise/​Mobility/​WiFiLBS-DG.pdf

This is an older design guide based on RSSI (Signal Strength) but has good best practice information to be used along with this deployment guide.

If you have not done so, now is the time to place AP's on the map using Prime 3.x noting the orientation of the Hyperlocation module. It is important to emphasis that the locations entered into Prime must be accurate.

Note	You must use the PI 3.0 or higher in order to set the orientation of the AP on the map. You will want to note the position of the AP on the map in CMX10.2.x (see Arrow or location marker “0 degree” on the AP).

For an overview on maps within Prime see the following URL. http:/​/​www.cisco.com/​c/​en/​us/​td/​docs/​wireless/​ncs/​1-0/​configuration/​guide/​NCS10cg/​maps.html

Figure 14. Hyperlocation array with azimuth marker location arrow (circled in red) needs to be indicated on the map

It is very important that you indicate on the PI map the orientation of the AP.

If your map has good granularity such as the map below, Enterprise indoor location map showing cubicles) then it should be easily able to determine client accuracy – If however, this is a warehouse or other large area, you may need to best determine accuracy by perhaps placing grid coordinates on the floor or fine tuning the maps with landmarks in your environment. Cisco Internal.

Figure 15. Enterprise Indoor Location Map Showing Cubicles

Note	You will want to limit your location assessments to active associated clients since Hyperlocation (in this release) only tracks associated clients.

At this point, you may want to spend some time performing location assessments using standard RSSI based location. This will allow you to verify the system works without the Hyperlocation components and gives you a baseline before going to Hyperlocation.

Please spend some time to get familiar with the environment and collect screenshots and location accuracy test should be completed without the Hyperlocation components enabled.

Setup many different clients associated to the network, note their positions on the map, perhaps run some baseline throughput testing, as it would be good to characterize the AP performance without Hyperlocation and then again using Hyperlocation.

At this point, baseline testing is complete and we can move to enabling the Hyperlocation module and testing location accuracy with the module enabled.

You can monitor the system to ensure that Hyperlocation packets are coming in and being process with the system GUI. The LOCATION tab has a METRIC for Hyperlocation calculations that can quickly be used to determine if Hyperlocation is functioning correctly.

This Metric is as shown. If this metric is zero, troubleshooting of the installation is required.

16113, 2003, 80, 443, ICMP, 161,162

It is important to understand the packet flow for Hyperlocation. Each AP is provided with the IP address and UDP port of the CMX10.2.1 server. It creates a packet that has all of the AoA information that it has generated and sends these packets at a rate of about 1 packet per second per AP to the WLC who uses an ARP to determine if it should send locally or send to the default gateway the packet as it is destined for the IP address for the CMX 10.2.1 server.

Run tcpdump –XX –i eth0 dst port 2003 on the CMX console; note this will require to be run as root; ctrl+C to break

This command is only required if there is issues with seeing the AoA Packet count increasing via the GUI.

At this point, the WLC and CMX 10.2.x should be able to communicate. You can verify that they are by looking at the controller list. If it is green then the controller is active and sending data that the CMX 10.2 system can parse.

If one has added a new WLC you may lose sync between the AP and the MSE. This will be evident if you no longer have traffic between the AP and MSE. The resolution should be to DELETE the WLC completely from the MSE and add it back. This issue is CSCuv93732 and will likely be resolved in a later release. This may also be resolved with reboot of the WLC. If you do not have sync between MSE and AP, please reboot the WLC.

If you have an NTP server that is 12 digits long, for example 100.100.100.100, the last digit may not be transferred to the AP to allow them to sync with the correct clock. This should be resolved by using an NTP server with 11 or less digits such as 100.10.10.10.

Some of the important components of this screen are:

• Connect client count at top.

• X,Y location of cursor on screen at bottom right

• The (*) cog button that changes the screen refresh rate (from 1 to 10 seconds)

• The search function that allows you to search for clients across floors.
  

  
  
  

CMX 10.2 has a series of API that can be executed by entering a REST API command into CHROME browser. It is recommended that you install browser extensions to parse JSON messages to make them easier to read. A suggested extension is JSON FORMATTER.

The method to use these API to check is to login to the CMX 10.2.x system, go to the location page and then open up another browser TAB on the same application. This ensures that your browser is authenticated for the request.

The first API is that is helpful for verifying that CMX 10.2.x is running correctly is http://CMX-IP/locationcontainer/container/

The results that you are looking for are below: AoA calculations are being performed.

A second API that is used is: http://CMX-IP/hyperlocationcontainer/container/This shows the rate at which Hyperlocation UDP data packets are coming into the CMX 10.2 system.

A third set of API’s are required to initiate a MAC trace.

The results of a MAC address trace are as follows:

A MAC trace is requested using a POSTMAN client with the following API…

Finally and API that helps to determine if the angle of the AP antenna is set correctly is http://CMXIP/api/config/v1/aps

The sample output from this is;

Note	The antenna angle above is in Radians, 1.57 Radians is 90 degrees. This API will be helpful in troubleshooting incorrectly placed antenna.

Short range for BLE beacons is considered to be 1 – 3 meters. But with a 10 ft ceiling mount, you must have this at a minimum of 3 meters. So, optimally the short range for an iPhone6 would be from -30 dBm to -32 dBm. The mid range is from 3 meters to 10 meters, so under ideal conditions this would be from -22 dBm to -28 dBm. The long range is greater than 10 meters, which would be from 0 dBm to -22 dBm.

Note	If you are mounted on a ceiling higher than 10 ft, you must start with medium range as a short range beacon because short range would not reach the floor.

Figure 22. Examining the BLE Beacon Settings

There is an iPhone app and Android app known iLocate from RADIUS NETWORKS”that to determine the signal strength of a received BEACON and has been validated to work with the Hyperlocation module.

When installing the App, make sure that you allow the app to use location services to detect Beacons.

The App should be programmed to listen for the specific UUID that is being beaconed by the Hyperlocation module. It will then report the signal strength that it hears and the different MAJOR and MINORS that are being beaconed out from the specific APS. If the signal strength is strong enough, the underlying OS calculates a distance, than this is also displayed. The algorithm as to when iOS displays a distance is not revealed by APPLE, but a distance is shown when the signal strength is high.

When a specific BEACON is selected, the specific RSSI of that Beacon detection is also shown. As well as the iOS calculated distance from the BEACON and the iOS inferred distance (i.e. “immediate, near or far”).

CMX 10.2 can display the location of BLE Beacons, including Beacons that are broadcast from the Hyperlocation module. In order to do this, CLEANAIR must be enabled on the WLC.

If CleanAir is enabled, then you need to enable interferer tracking on the CMX at the following tracking location tab in the services menu.

The interferers box needs to be enabled to track BLE Beacon location.

To display BLE Beacons, you need to enable them in the Location tab of an MSE. This filtering occurs on this page.

Note	Beacons that come from access point are displayed as ROUGE until they are classified.It can take 10-12 minutes after a beacon has started broadcasting to be located on this screen.

When it is located on this screen you should be able to see the UUID, MAJOR and MINOR when clicking on a beacon as follows.

There is also a CLI command that allows you to determine what the WLC sees as Beacons.

test clearair show idr all

Figure 23.

Here are some of the CMX 10.2 CLI commands:

- cmxctl version (check build version)
- cmxctl stop -a (stop all services)
- cmxctl restart (restart CMX services)
- cmxctl start (start CMX services)
- cmxctl status (check status of CMX services)
- cmxctl config controllers add (add controller/s)
- cmxctl config controllers show
- cmxctl config maps import (you can either provide PI credentials for MSE to 
grab maps or put map export file in /opt and give file path /opt/pi_export_file)
- cmxconfig maps delete (delete campus, have to give name).

// set up the UUIDs (on a per controller basis)
Config advanced hyperlocation ble-beacon beacon-id 1 add uuid 11111111-1111-1111-1111-111111111111
Config advanced hyperlocation ble-beacon beacon-id 2 add uuid 22222222-2222-2222-2222-222222222222
Config advanced hyperlocation ble-beacon beacon-id 3 add uuid 33333333-3333-3333-3333-333333333333
Config advanced hyperlocation ble-beacon beacon-id 4 add uuid 44444444-4444-4444-4444-444444444444
Config advanced hyperlocation ble-beacon beacon-id 5 add uuid 55555555-5555-5555-5555-555555555555

// set up the majors (on a per AP basis)
Config advanced hyperlocation ble-beacon beacon-id 1 add ap-name <AP NAME> major 1001
Config advanced hyperlocation ble-beacon beacon-id 2 add ap-name <AP NAME> major 2002
Config advanced hyperlocation ble-beacon beacon-id 3 add ap-name <AP NAME> major 3003
Config advanced hyperlocation ble-beacon beacon-id 4 add ap-name <AP NAME> major 4004
Config advanced hyperlocation ble-beacon beacon-id 5 add ap-name <AP NAME> major 5005

// Set up the minors (on a per AP basis)
Config advanced hyperlocation ble-beacon beacon-id 1 add ap-name <AP NAME> minor 10
Config advanced hyperlocation ble-beacon beacon-id 2 add ap-name <AP NAME> minor 11
Config advanced hyperlocation ble-beacon beacon-id 3 add ap-name <AP NAME> minor 12
Config advanced hyperlocation ble-beacon beacon-id 4 add ap-name <AP NAME> minor 13
Config advanced hyperlocation ble-beacon beacon-id 5 add ap-name <AP NAME> minor 14

// Set up the Attenuation (Tx Power) (on a per AP basis)
Config advanced hyperlocation ble-beacon beacon-id 1 add ap-name <AP NAME> txpwr 0
Config advanced hyperlocation ble-beacon beacon-id 2 add ap-name <AP NAME> txpwr 10
Config advanced hyperlocation ble-beacon beacon-id 3 add ap-name <AP NAME> txpwr 20
Config advanced hyperlocation ble-beacon beacon-id 4 add ap-name <AP NAME> txpwr 30
Config advanced hyperlocation ble-beacon beacon-id 5 add ap-name <AP NAME> txpwr 40

// set up the transmission frequency (on a per Controller basis)
Config advanced hyperlocation ble-beacon interval 10

// turn individual beacons on/off (enable/disable) (on a per Controller basis)
Config advanced hyperlocation ble-beacon beacon-id 1 enable
Config advanced hyperlocation ble-beacon beacon-id 2 enable
Config advanced hyperlocation ble-beacon beacon-id 3 enable
Config advanced hyperlocation ble-beacon beacon-id 4 enable
Config advanced hyperlocation ble-beacon beacon-id 5 enable

Note that I do not know the id of the AP you will be using and its name/id should be substituted where it says <AP NAME> above.

Using the above configuration will result in the following ble-beacons each being generated at a 10 Hz frequency:

# UUID                              Major Minor Attenuation
Beacon 1 11111111-1111-1111-1111-111111111111 1001 10    0
Beacon 2 22222222-2222-2222-2222-222222222222 2002 11   10
Beacon 3 33333333-3333-3333-3333-333333333333 3003 12   20
Beacon 4 44444444-4444-4444-4444-444444444444 4004 13   30
Beacon 5 55555555-5555-5555-5555-555555555555 5005 14   40
Cisco Internal Use Only
Copyright © 2015 Cisco Systems, Inc. All rights reserved.
Page 56

1. Check that AP are seen and up on WLC

2. Check that the AP have the correct antenna setting

3. Check that the Hyperlocation setting are set

4. Check that the WLC can ping the CMX 10.2

1. Check that PRIME is able to see the WLC

2. Check that the AP are seen by PRIME

3. Check that the AP are correctly placed on the map

4. Check the dimensions on the map

5. Check the placement of the AP on the map

1. Check that the controller is online

2. Check that Hyperlocation is enabled

3. Check that the maps are seen in DETECT / LOCATE

4. Check that clients are seen on the map

5. Check that filter of unassociated clients is enabled (optional)

Procedure

(Cisco Controller) >debug nmsp events enable
(Cisco Controller) >debug nmsp errors enable
(Cisco Controller) >debug capwap info enable

AP1__84b8.0252.b930#show capwap rm hyperlocation level1-list

Level-1 List for 2.4GHz Band
----------------------------
Channel Width Serving MAC     Max Clients
------- ----- -------------- -----------
1          0 f07f.0635.2d40    8
1          0 f4cf.e272.4ed0    8
1          0 84b8.0265.5540    8
1          0 84b8.025d.b930    8

Level-1 List for 5GHz Band
----------------------------
Channel Width Serving MAC     Max Clients
------- ----- -------------- -----------
36 0     84b8.025d.b930             8
36 0     f07f.0635.2d40             8
36 0     f4cf.e272.4ed0             8
36 0     84b8.0265.5540             8

P1__84b8.0252.b930#debug capwap rm prl events
CAPWAP RM PRL events display debugging is on
Aug 14 06:57:47.441: PRL: ntpSyncSetL1Idx: 0 ntpSyncSetL2Idx: 0
Aug 14 06:57:47.517: PRL: PAK RSSI Report: 0
Aug 14 06:57:47.517: PRL: reported client entries: 0 of 0, final: 1
Aug 14 06:57:47.517: PRL: tblFullCnt: 0, AP entries: 19
Aug 14 06:57:47.677: PRL: ntpSyncChanIdx: 6 duration: 143
Aug 14 06:57:47.677: PRL: ntpSyncSetL1Idx: 0 ntpSyncSetL2Idx: 3
Aug 14 06:57:47.677: PRL: band: 2 channel submitted: 64 width: 0
Aug 14 06:57:47.821: PRL: ntpSyncChanIdx: 0 duration: 249
Aug 14 06:57:47.821: PRL: ntpSyncSetL1Idx: 4 ntpSyncSetL2Idx: 0
Aug 14 06:57:47.821: PRL: band: 2 channel submitted: 36 width: 0
Aug 14 06:57:48.017: PRL: PAK RSSI Report: 0
Aug 14 06:57:48.017: PRL: reported client entries: 1 of 1, final: 1
Aug 14 06:57:48.017: PRL: tblFullCnt: 0, AP entries: 19

Procedure

AP1__84b8.0252.b930#debug dot11 hyperlocation-BAR general
dot11 HALO BAR debugging is on:
Aug 14 07:08:59.815: HYPERLOCATION_BAR:Scanning chan 1 on radio 0
Aug 14 07:08:59.815: HYPERLOCATION_BAR:Chan 1 on radio 0 is supported on this AP
Aug 14 07:08:59.847: HYPERLOCATION_BAR:Timer for radio 0 expired
Aug 14 07:08:59.847: HYPERLOCATION_BAR:Dwell Duration - 0 ms
Aug 14 07:09:00.071: HYPERLOCATION_BAR:Scanning chan 36 on radio 1
Aug 14 07:09:00.071: HYPERLOCATION_BAR:Chan 36 on radio 1 is supported on this AP
Aug 14 07:09:00.103: HYPERLOCATION_BAR:Timer for radio 1 expired
Aug 14 07:09:00.103: HYPERLOCATION_BAR:Dwell Duration - 15 ms
Aug 14 07:09:00.103: HYPERLOCATION_BAR:Client-240a.6473.2d0f:Seq-1,
  BARs Sent-15,BARs Done-15,Duration-3 ms,State-AWAKE
Aug 14 07:09:00.103: HYPERLOCATION_BAR:Client-3c77.e643.05f7:Seq-2,
  BARs Sent-15,BARs Done-15,Duration-3 ms,State-AWAKE
Aug 14 07:09:00.103: HYPERLOCATION_BAR:LMA frame sent.
Aug 14 07:09:00.319: HYPERLOCATION_BAR:
Hyperlocation dwell collection complete. MSE record len = 113

AP1__84b8.0252.b930#debug dot11 hyperlocation-BAR general
dot11 HALO BAR debugging is on:
Hyperlocation dwell collection complete. MSE record len = 98
Report byte dump:
0x00 0x84 0xB8 0x02 0x5D 0xB9 0x30 0x8B 0x5B 0x5B 0x01 0x81 0x24 0x0A 0x02 0x3C:
0x30 0x52
Aug 14 07:11:50.359: HYPERLOCATION_BAR:
Version = 0
AP base mac = 84:B8:02:5D:B9:30
TS = 0x8B5B5B
Num Dwell records = 1
Aug 14 07:11:50.359: HYPERLOCATION_BAR:
type = 1
bms = 4
channel = 36
R[7]-BandID[6-3]-SlotID[2-0] = 0x0A
num of client records = 2
Aug 14 07:11:50.359: HYPERLOCATION_BAR:
Client[0 ].mac = 3C:77:E6:43:05:F7
Client[0 ].RelTS = 25
Client[0 ].RSSI = -52 (0xCC)
Client[0 ].antmap = 0xFFFFFFFF
Client[0 ].error = 15
Aug 14 07:11:50.359: HYPERLOCATION_BAR:
Client[0 ].antval[0 ] = 0x0135
Client[0 ].antval[1 ] = 0x016A
Client[0 ].antval[2 ] = 0x0117:

AP1__84b8.0252.b930#show capwap client traffic | Include Hyperlocation
Hyperlocation Packets transmitted : 297515
AP1__84b8.0252.b930#show capwap client traffic | Include Hyperlocation
Hyperlocation Packets transmitted : 297528
AP1__84b8.0252.b930#show capwap client traffic | Include Hyperlocation
Hyperlocation Packets transmitted : 297548

(Cisco Controller) >debug fastpath dump stats
FP0.00:
FP0.00: OK - RX (Hyperlocation) from AP : 1406890 (+ 1406890)
FP0.00: OK - TX (Hyperlocation) to MSE : 1406890 (+ 1406890):
(Cisco Controller) >debug fastpath dump stats
FP0.00:
FP0.00: OK - RX (Hyperlocation) from AP : 1407016 (+ 126)
FP0.00: OK - TX (Hyperlocation) to MSE : 1407016 (+ 126)