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

hi all

we are currently migrating our locations from traditional to aruba central managed.

replacing our hardware with newer ones per location.

on of the services we use is BLE beaconing/scanning in combination with Meridian. we currently use mobility conductor to collect and send it to meridian.

since aruba central does not have this function by default you need to use a collector which is called IOT connector to collect the ble data and send it.

so we've set up a vm of IOT collector and configured it according to the documentation: IoT Operations (arubanetworks.com)

but it doesnt work as it should. it does show up in aruba central after registering it

but after a while the status of the iot connector shows up as offline.

after troubleshooting it we noticed that a lot of the traffic is being blocked by our firewall although we've created rules for the destinations that needs to be reachable.

the TAC engineer suggests just to allow the traffic that is being blocked. but i dont think that he understand that we have company policies that we need to follow we cannot 'just' allow traffic that is blocked especially if it is not documented.

so my question is does someone else the same issue with the iot connector and perhaps advice?

Hello, 

Here is the Aruba Central IoT Operations documentation about opening firewall ports for IoT Connector communication.

Please check if you have opened all required communication. If so, your IoT Connector should have a stable connection.

By the way, for Meridian to work with AOS10/IoT-Ops deployments, you will need the Meridian App for IoT-Ops, which is not yet released. So even if your IoT Connector works, you will not be able to deploy the full solution yet. I suggest you contact your local Aruba SE or sales for support on this.

Best regards,

Jens

hi all

we are currently migrating our locations from traditional to aruba central managed.

replacing our hardware with newer ones per location.

on of the services we use is BLE beaconing/scanning in combination with Meridian. we currently use mobility conductor to collect and send it to meridian.

since aruba central does not have this function by default you need to use a collector which is called IOT connector to collect the ble data and send it.

so we've set up a vm of IOT collector and configured it according to the documentation: IoT Operations (arubanetworks.com)

but it doesnt work as it should. it does show up in aruba central after registering it

but after a while the status of the iot connector shows up as offline.

after troubleshooting it we noticed that a lot of the traffic is being blocked by our firewall although we've created rules for the destinations that needs to be reachable.

the TAC engineer suggests just to allow the traffic that is being blocked. but i dont think that he understand that we have company policies that we need to follow we cannot 'just' allow traffic that is blocked especially if it is not documented.

so my question is does someone else the same issue with the iot connector and perhaps advice?

hi 

there is a documentation to configure the meridian app in aruba central under iot applications: ArubaOS 10 Meridian Beacons Management and Asset Tracking Configuration Guide – Meridian Platform Documentation (meridianapps.com)

but indeed i noticed that the app is not available in aruba central to install & configure

is the app still in development? it would be weird if they publish a document for something that is not available?

Hello, 

Here is the Aruba Central IoT Operations documentation about opening firewall ports for IoT Connector communication.

Please check if you have opened all required communication. If so, your IoT Connector should have a stable connection.

By the way, for Meridian to work with AOS10/IoT-Ops deployments, you will need the Meridian App for IoT-Ops, which is not yet released. So even if your IoT Connector works, you will not be able to deploy the full solution yet. I suggest you contact your local Aruba SE or sales for support on this.

Best regards,

Jens

hi all

we are currently migrating our locations from traditional to aruba central managed.

replacing our hardware with newer ones per location.

on of the services we use is BLE beaconing/scanning in combination with Meridian. we currently use mobility conductor to collect and send it to meridian.

since aruba central does not have this function by default you need to use a collector which is called IOT connector to collect the ble data and send it.

so we've set up a vm of IOT collector and configured it according to the documentation: IoT Operations (arubanetworks.com)

but it doesnt work as it should. it does show up in aruba central after registering it

but after a while the status of the iot connector shows up as offline.

after troubleshooting it we noticed that a lot of the traffic is being blocked by our firewall although we've created rules for the destinations that needs to be reachable.

the TAC engineer suggests just to allow the traffic that is being blocked. but i dont think that he understand that we have company policies that we need to follow we cannot 'just' allow traffic that is blocked especially if it is not documented.

so my question is does someone else the same issue with the iot connector and perhaps advice?

Hi, 

The documentation was released earlier than planned, sorry if that caused any confusion.

The app is currently in internal testing and is scheduled for release in early 2024.

Also, the app will require AOS 10.5.1.0 to run on the access points, which is scheduled to be released in Feb'24. 

Hope this helps.

Best regards, 

Jens

hi 

there is a documentation to configure the meridian app in aruba central under iot applications: ArubaOS 10 Meridian Beacons Management and Asset Tracking Configuration Guide – Meridian Platform Documentation (meridianapps.com)

but indeed i noticed that the app is not available in aruba central to install & configure

is the app still in development? it would be weird if they publish a document for something that is not available?

Hello, 

Here is the Aruba Central IoT Operations documentation about opening firewall ports for IoT Connector communication.

Please check if you have opened all required communication. If so, your IoT Connector should have a stable connection.

By the way, for Meridian to work with AOS10/IoT-Ops deployments, you will need the Meridian App for IoT-Ops, which is not yet released. So even if your IoT Connector works, you will not be able to deploy the full solution yet. I suggest you contact your local Aruba SE or sales for support on this.

Best regards,

Jens

hi all

we are currently migrating our locations from traditional to aruba central managed.

replacing our hardware with newer ones per location.

on of the services we use is BLE beaconing/scanning in combination with Meridian. we currently use mobility conductor to collect and send it to meridian.

since aruba central does not have this function by default you need to use a collector which is called IOT connector to collect the ble data and send it.

so we've set up a vm of IOT collector and configured it according to the documentation: IoT Operations (arubanetworks.com)

but it doesnt work as it should. it does show up in aruba central after registering it

but after a while the status of the iot connector shows up as offline.

after troubleshooting it we noticed that a lot of the traffic is being blocked by our firewall although we've created rules for the destinations that needs to be reachable.

the TAC engineer suggests just to allow the traffic that is being blocked. but i dont think that he understand that we have company policies that we need to follow we cannot 'just' allow traffic that is blocked especially if it is not documented.

so my question is does someone else the same issue with the iot connector and perhaps advice?