Developer

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

I have an HPE account but it's not tied to the university account so I can't download those documents.  They may approve (we'll see - I don't work for the IT department).  However, I did find what I think is an older version of the .proto file.  It doesn't have a version number in it, but the document name is HPE_a00058376en_us_Aruba Telemetry API Proto File.proto and everything in it seems to jibe with the sample file, which is great.

It does not have apHealthUpdate in it anywhere, though, which is what makes me think it's a little out of date.

It was basically trivial to protoc this file into something that works from go, and from that, make a websocket server that receives telemetry messages and parses the protobuf.  If I were to take out all the comments, then you can make a server that spits out the beacons in 10 or 12 lines of go.  I definitely have some questions about some of the usage, though.  Most of them are pretty simple, and if I had access to hardware I would just try it.  My contact at our ITS dept may have an AP-303h so if he's feeling generous with his time I'm hoping he can use a campus controller to convert it to an IAP and let me borrow it.

So a basic question about the format: A report has a Reported[] array.  Each item in that array has a mac address (of the found item), then it has a beacons[] array.  In the JSON example, the beacons[] array has a ibeacon object and an eddystone object.  Is it really likely that a single beacon would have both (dual format) ?  Or would it typically be either one or the other?

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

I have an HPE account but it's not tied to the university account so I can't download those documents.  They may approve (we'll see - I don't work for the IT department).  However, I did find what I think is an older version of the .proto file.  It doesn't have a version number in it, but the document name is HPE_a00058376en_us_Aruba Telemetry API Proto File.proto and everything in it seems to jibe with the sample file, which is great.

It does not have apHealthUpdate in it anywhere, though, which is what makes me think it's a little out of date.

It was basically trivial to protoc this file into something that works from go, and from that, make a websocket server that receives telemetry messages and parses the protobuf.  If I were to take out all the comments, then you can make a server that spits out the beacons in 10 or 12 lines of go.  I definitely have some questions about some of the usage, though.  Most of them are pretty simple, and if I had access to hardware I would just try it.  My contact at our ITS dept may have an AP-303h so if he's feeling generous with his time I'm hoping he can use a campus controller to convert it to an IAP and let me borrow it.

So a basic question about the format: A report has a Reported[] array.  Each item in that array has a mac address (of the found item), then it has a beacons[] array.  In the JSON example, the beacons[] array has a ibeacon object and an eddystone object.  Is it really likely that a single beacon would have both (dual format) ?  Or would it typically be either one or the other?

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

message Beacons {
    optional  Ibeacon     ibeacon           = 1;
    optional  Eddystone   eddystone         = 2;
//  reserved                                  3;
}

I have an HPE account but it's not tied to the university account so I can't download those documents.  They may approve (we'll see - I don't work for the IT department).  However, I did find what I think is an older version of the .proto file.  It doesn't have a version number in it, but the document name is HPE_a00058376en_us_Aruba Telemetry API Proto File.proto and everything in it seems to jibe with the sample file, which is great.

It does not have apHealthUpdate in it anywhere, though, which is what makes me think it's a little out of date.

It was basically trivial to protoc this file into something that works from go, and from that, make a websocket server that receives telemetry messages and parses the protobuf.  If I were to take out all the comments, then you can make a server that spits out the beacons in 10 or 12 lines of go.  I definitely have some questions about some of the usage, though.  Most of them are pretty simple, and if I had access to hardware I would just try it.  My contact at our ITS dept may have an AP-303h so if he's feeling generous with his time I'm hoping he can use a campus controller to convert it to an IAP and let me borrow it.

So a basic question about the format: A report has a Reported[] array.  Each item in that array has a mac address (of the found item), then it has a beacons[] array.  In the JSON example, the beacons[] array has a ibeacon object and an eddystone object.  Is it really likely that a single beacon would have both (dual format) ?  Or would it typically be either one or the other?

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

message Beacons {
    optional  Ibeacon     ibeacon           = 1;
    optional  Eddystone   eddystone         = 2;
//  reserved                                  3;
}

I have an HPE account but it's not tied to the university account so I can't download those documents.  They may approve (we'll see - I don't work for the IT department).  However, I did find what I think is an older version of the .proto file.  It doesn't have a version number in it, but the document name is HPE_a00058376en_us_Aruba Telemetry API Proto File.proto and everything in it seems to jibe with the sample file, which is great.

It does not have apHealthUpdate in it anywhere, though, which is what makes me think it's a little out of date.

It was basically trivial to protoc this file into something that works from go, and from that, make a websocket server that receives telemetry messages and parses the protobuf.  If I were to take out all the comments, then you can make a server that spits out the beacons in 10 or 12 lines of go.  I definitely have some questions about some of the usage, though.  Most of them are pretty simple, and if I had access to hardware I would just try it.  My contact at our ITS dept may have an AP-303h so if he's feeling generous with his time I'm hoping he can use a campus controller to convert it to an IAP and let me borrow it.

So a basic question about the format: A report has a Reported[] array.  Each item in that array has a mac address (of the found item), then it has a beacons[] array.  In the JSON example, the beacons[] array has a ibeacon object and an eddystone object.  Is it really likely that a single beacon would have both (dual format) ?  Or would it typically be either one or the other?

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

/* TLM advertising data: */uint8_t advdata_tlm[] ={  0x03,  // Length  0x03,  // Param: Service List  0xAA, 0xFE,  // Eddystone ID  0x11,  // Length  0x16,  // Service Data  0xAA, 0xFE, // Eddystone ID  0x20,  // TLM flag  0x00, // TLM version  /* [10] */ 0x00, 0x00,  // Battery voltage  /* [12] */ 0x80, 0x00,  // Beacon temperature  /* [14] */ 0x00, 0x00, 0x00, 0x00, // Advertising PDU count  /* [18] */ 0x00, 0x00, 0x00, 0x00 // Time since reboot};

message Beacons {
    optional  Ibeacon     ibeacon           = 1;
    optional  Eddystone   eddystone         = 2;
//  reserved                                  3;
}

I have an HPE account but it's not tied to the university account so I can't download those documents.  They may approve (we'll see - I don't work for the IT department).  However, I did find what I think is an older version of the .proto file.  It doesn't have a version number in it, but the document name is HPE_a00058376en_us_Aruba Telemetry API Proto File.proto and everything in it seems to jibe with the sample file, which is great.

It does not have apHealthUpdate in it anywhere, though, which is what makes me think it's a little out of date.

It was basically trivial to protoc this file into something that works from go, and from that, make a websocket server that receives telemetry messages and parses the protobuf.  If I were to take out all the comments, then you can make a server that spits out the beacons in 10 or 12 lines of go.  I definitely have some questions about some of the usage, though.  Most of them are pretty simple, and if I had access to hardware I would just try it.  My contact at our ITS dept may have an AP-303h so if he's feeling generous with his time I'm hoping he can use a campus controller to convert it to an IAP and let me borrow it.

So a basic question about the format: A report has a Reported[] array.  Each item in that array has a mac address (of the found item), then it has a beacons[] array.  In the JSON example, the beacons[] array has a ibeacon object and an eddystone object.  Is it really likely that a single beacon would have both (dual format) ?  Or would it typically be either one or the other?

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

message Beacons {
    optional  Ibeacon     ibeacon           = 1;
    optional  Eddystone   eddystone         = 2;
//  reserved                                  3;
}

I have an HPE account but it's not tied to the university account so I can't download those documents.  They may approve (we'll see - I don't work for the IT department).  However, I did find what I think is an older version of the .proto file.  It doesn't have a version number in it, but the document name is HPE_a00058376en_us_Aruba Telemetry API Proto File.proto and everything in it seems to jibe with the sample file, which is great.

It does not have apHealthUpdate in it anywhere, though, which is what makes me think it's a little out of date.

It was basically trivial to protoc this file into something that works from go, and from that, make a websocket server that receives telemetry messages and parses the protobuf.  If I were to take out all the comments, then you can make a server that spits out the beacons in 10 or 12 lines of go.  I definitely have some questions about some of the usage, though.  Most of them are pretty simple, and if I had access to hardware I would just try it.  My contact at our ITS dept may have an AP-303h so if he's feeling generous with his time I'm hoping he can use a campus controller to convert it to an IAP and let me borrow it.

So a basic question about the format: A report has a Reported[] array.  Each item in that array has a mac address (of the found item), then it has a beacons[] array.  In the JSON example, the beacons[] array has a ibeacon object and an eddystone object.  Is it really likely that a single beacon would have both (dual format) ?  Or would it typically be either one or the other?

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris

Hi Jens,

Firstly, thanks for your detailed answers in this forum.

I saw your reply about the BLE data forwarding service and in particular the sentence here:

"Unfortunately, BLE data forwarding is only supported for known BLE vendors (requiring Aruba SW version 8.8 or higher)"

I'm trying to get a large Aruba network to forward all BLE data packets for all types of devices,  so essential to get as much data from nearby devices as possible, the scope is e.g. to measure wait times. ( I know about the telemetry interface, but if we can make the BLE data interface work this would have better data for our case) 

I read the quoted reply as I would have to ask the system to get BLEData for known BLE vendors ... is that via the Vendor Filter ? .. can this filter contain multiple at the same time ? Is there another way to get a system to report BLEData for virtually all devices in the range ?  Can you register your own device class filters, .. and e.g. register a very general one ? 

Thanks for your support

Best regards

Lars Tørholm

message Beacons {
    optional  Ibeacon     ibeacon           = 1;
    optional  Eddystone   eddystone         = 2;
//  reserved                                  3;
}

I have an HPE account but it's not tied to the university account so I can't download those documents.  They may approve (we'll see - I don't work for the IT department).  However, I did find what I think is an older version of the .proto file.  It doesn't have a version number in it, but the document name is HPE_a00058376en_us_Aruba Telemetry API Proto File.proto and everything in it seems to jibe with the sample file, which is great.

It does not have apHealthUpdate in it anywhere, though, which is what makes me think it's a little out of date.

It was basically trivial to protoc this file into something that works from go, and from that, make a websocket server that receives telemetry messages and parses the protobuf.  If I were to take out all the comments, then you can make a server that spits out the beacons in 10 or 12 lines of go.  I definitely have some questions about some of the usage, though.  Most of them are pretty simple, and if I had access to hardware I would just try it.  My contact at our ITS dept may have an AP-303h so if he's feeling generous with his time I'm hoping he can use a campus controller to convert it to an IAP and let me borrow it.

So a basic question about the format: A report has a Reported[] array.  Each item in that array has a mac address (of the found item), then it has a beacons[] array.  In the JSON example, the beacons[] array has a ibeacon object and an eddystone object.  Is it really likely that a single beacon would have both (dual format) ?  Or would it typically be either one or the other?

Transport Interval. The transport interval determines how often IoT or BLE data is sent from BD to BR. ArubaOS supports the following transport intervals:Asset tag RSSI data is sent every 4 seconds from each AP to MeridianAruba beacon management data is sent every 30 minutes

If I understand this, the BR is the BLE Relay, another program that runs on each individual AP.  The BR collects the beacons it hears from the BD process, and, if configured correctly, it can push them somewhere of your choosing: either an HTTPS POST to somewhere, or over a websocket.  This has to be done on each individual access point, in my case that's thousands of them.  They then all individually will HTTP POST their 'heard beacons' tables to an endpoint of my choosing.

This leads to some questions, based on my limited understanding of how this works.

First, is the format of these messages defined somewhere I can see (a url etc.)?  I gather that if it is HTTP POST that it's JSON (what's the format?) and if it's via websocket it's protobuf (where can i find the .proto definitions?)

Second, if I have this right, then I'll need to stand up a server that can handle a LOT of concurrent connections (7,500 access points).  Do I have that right?  Can these APs be configured to only send changes?

Third, there is some notion of filtering.  That might be useful for me but I think to do that I would have to maintain a list of UUIDs and push them to every single access point.  Do I have that right?  I don't think I can use this but I still would like to know how it works.  It sounds like a useful way to limit traffic, but I might want to limit what users see what (i.e. have multiple whitelists).  Based on that, I think I need to have my own central server receive everything, then filter based on the individual user or client.

Finally ... if I bought just one aruba access point for home (like an AP22) could I experiment with all of this without being tied to the full campus environment, Aruba Central, etc.?

--Chris