Internet of Things (IoT) and Industrial IoT (IIoT)

Hi.
I am working with 505 and 515 APs. Internal radio is configured for beaconing and scanning.  Beacons are configured with the same UUID and major but unique minors. Beaconing interval is 1000ms.   Beaconing is working fine as I can detect the beacons using a different ibeacon scanning apps.
I have a Transport configured to send BLE telemetry to a websocket endpoint. That too works well as I am getting BLE telemetry from all APs.
However, I noticed that the telemetry from each AP never includes its own internal radio BLE advertisement data. It has data of the internal beacon of nearby APs plus any other ibeacon devices in the UUID filter as expected, but not its own.
I further confirmed this by checking the BLE table on each AP using the CLI (#show ap debug ble-table ap-name <ap-name> ibeacon). On each AP, it contains data of nearby beacons including other APs, but not of its own internal beacon.
Is this expected behavior and is there some way to change it so that each AP can also report on its own internal beacon?

Thanks.

Hi.
I am working with 505 and 515 APs. Internal radio is configured for beaconing and scanning.  Beacons are configured with the same UUID and major but unique minors. Beaconing interval is 1000ms.   Beaconing is working fine as I can detect the beacons using a different ibeacon scanning apps.
I have a Transport configured to send BLE telemetry to a websocket endpoint. That too works well as I am getting BLE telemetry from all APs.
However, I noticed that the telemetry from each AP never includes its own internal radio BLE advertisement data. It has data of the internal beacon of nearby APs plus any other ibeacon devices in the UUID filter as expected, but not its own.
I further confirmed this by checking the BLE table on each AP using the CLI (#show ap debug ble-table ap-name <ap-name> ibeacon). On each AP, it contains data of nearby beacons including other APs, but not of its own internal beacon.
Is this expected behavior and is there some way to change it so that each AP can also report on its own internal beacon?

Thanks.

Hi.
I am working with 505 and 515 APs. Internal radio is configured for beaconing and scanning.  Beacons are configured with the same UUID and major but unique minors. Beaconing interval is 1000ms.   Beaconing is working fine as I can detect the beacons using a different ibeacon scanning apps.
I have a Transport configured to send BLE telemetry to a websocket endpoint. That too works well as I am getting BLE telemetry from all APs.
However, I noticed that the telemetry from each AP never includes its own internal radio BLE advertisement data. It has data of the internal beacon of nearby APs plus any other ibeacon devices in the UUID filter as expected, but not its own.
I further confirmed this by checking the BLE table on each AP using the CLI (#show ap debug ble-table ap-name <ap-name> ibeacon). On each AP, it contains data of nearby beacons including other APs, but not of its own internal beacon.
Is this expected behavior and is there some way to change it so that each AP can also report on its own internal beacon?

Thanks.

Since ArubaOS/Aruba Instant 8.11 your are able to get the configured iBeacon configuration of an AP IoT radio using the ApHealthUpdate messages via the IoT websocket connection. We extended the AP status messages with more detailed information about the radio configuration including the iBeacon advertisement settings. 
ApHealthUpdate messages are send every 120 s for every AP. 

Hi.
I am working with 505 and 515 APs. Internal radio is configured for beaconing and scanning.  Beacons are configured with the same UUID and major but unique minors. Beaconing interval is 1000ms.   Beaconing is working fine as I can detect the beacons using a different ibeacon scanning apps.
I have a Transport configured to send BLE telemetry to a websocket endpoint. That too works well as I am getting BLE telemetry from all APs.
However, I noticed that the telemetry from each AP never includes its own internal radio BLE advertisement data. It has data of the internal beacon of nearby APs plus any other ibeacon devices in the UUID filter as expected, but not its own.
I further confirmed this by checking the BLE table on each AP using the CLI (#show ap debug ble-table ap-name <ap-name> ibeacon). On each AP, it contains data of nearby beacons including other APs, but not of its own internal beacon.
Is this expected behavior and is there some way to change it so that each AP can also report on its own internal beacon?

Thanks.