Search the Community
- ClearPass Recipe Review
- ClearPass Recipe Submission
- Admin Tool - Assign Role in Bulk
- Admin Tool - User Search
- CWNP Conf 2015
- Airheads Conference Vegas 2015
- Wlan Pro Conference 2015
- Airheads Conference Shanghai 2014
- WLAN Pro Conf EU 2014
- CWNP Conference 2014 (Sep 22 - 24)
- Airheads Local 2014
- Wireless Field Day 7 (Aug 6-8, 2014)
- Black Hat 2014 Contest
- Airheads EMEA Italy 2014 (June 9 - 13)
- Americas Airheads Conference 2014
- WLAN Professionals Summit 2014
- Airheads Roadshow 2013
- EMEA Airheads Conference 2013
- APJ Airheads Conference 2013
- Americas Airheads Conference 2013
- Americas Airheads Conference 2012
- APJ Airheads Conference 2012
- EMEA Airheads Conference 2012
- Airheads EMEA 2012 Contest: How to Enter - Contest Terms & Conditions
- Airheads EMEA 2012 Contest: Create your Entry to Win Here!
- Airheads Conferences Prior to 2012
- Americas Airheads Local Events 2012
- EMEA Airheads Local Events 2012
- Wireless Field Day 3 @ Aruba Networks
- Wireless Tech Field Day 2- Silicon Valley
- Wi-Fi Mobility Symposium- San Jose, CA USA
- SDN Apps
- Connector Translation Testing area
Hi, Vectorizing a map yourself will take up a lot of effort, better keep it through the Meridian t...
Vectorizing a map yourself will take up a lot of effort, better keep it through the Meridian team.
That being said, you can do some work on vectorizing a map yourself, but there are a lot of layers (the map advanced formatting on Meridian will give you an idea: http://docs.meridianapps.com/developers/map_layer_styling) that you would have to pay attention to and format and set in the right order. Assuming you have the right map vectorized, you will still need to save it in the right format and upload it using the Meridian maps APIs.
A good start would be to download an already vectorized map, check it out and edit it, then upload it to a new building to test your results.
Otherwise, stick to vectorizing through the Meridian team by creating your building/floor and then requesting the conversion by sending an email with your map file and map ID reference that you've created - instructions appear when you create that new floor on Meridian (it's free as long as you have an active subscription).
I believe it is one or other, Central or Airwave. You must choose. Central has clarity, you simp...I believe it is one or other, Central or Airwave. You must choose.
Central has clarity, you simply need a token (not sure if it is still in BETA but your local Aruba rep can tell you).
I do not believe requires visualRF floorplans but you can definitely use ALE with central as there is an option to enable it.
Mike, We could add around 100 controllers and 8 Airwave in single ALE server but shoul...
We could add around 100 controllers and 8 Airwave in single ALE server but should not cross the APs limit mentioned in the server sizing guide.
So if you are planning to add individual VCs then max we could add 100 entries in single ALE.
Hi Jeff, I'm the Meridian team's technical writer. We've had some questions about Meridi...
I'm the Meridian team's technical writer. We've had some questions about Meridian and personally identifiable information come up before, so I thought I'd take a little time to explain how all of this works.
In short: Meridian-powered apps do not send personally identifiable information to anyone, whether the Meridian server or a third-party.
Meridian-powered apps use Bluetooth signals generated from Aruba Beacons to calculate a user's current location and also to send notifications--what we call campaigns.
When Aruba Beacons are configured for proximity, they can either send a notification message to the end-user's device or send data along to a third-party server. These campaigns are configured by the Meridian administrator for a particular location. In some cases, for example, a Meridian-powered app may have a user login. A campaign could send that user ID to a third-party endpoint when that user enters a specific area in a location.
By default, though, when a campaign is triggered, no personally identifiable data is sent.
On iOS, the Meridian-powered app sends its identifierForVendor value. On Android, it sends its advertising ID. These are used for the purposes of cooldowns, so that a user doesn't continue to receive the same notification over and over again. These two values can't be used to personally identify someone.
I hope this helps answer your questions. If not, I'm happy to clarify anything that isn't clear.
For more information on this, please see documentation:
Hi Fabio, It's possible to import event feeds in XML, RSS, iCal, and JSON formats. ...
It's possible to import event feeds in XML, RSS, iCal, and JSON formats.
We have some documentation about importing feeds into the Editor here:
Let me know if you have any questions.
Meridian Technical Writer
I solved it with iCal synchronisation
Hi Pierre, Our Meridian team has taken a look at your screenshots and determined that th...
Our Meridian team has taken a look at your screenshots and determined that this isn't a bug. It's expected behavior for different devices to display the map differently. Even the same device with different resolution settings would display things differently.
I hope this helps address your concerns.
Pierre, The AS-100 should be provisioned and configured with the 'Beacons' app that is available ...
The AS-100 should be provisioned and configured with the 'Beacons' app that is available from the Apple App Store. Configuration is done from the Meridian App platform (edit.meridianapps.com).
CLI configuration is not recommended, nor supported.
Please make sure that you updated the Beacons App to the latest version, and you are close to your sensor (within few feet/meter). If you have another IOS device available, it may work to retry with that. If you still have problems that the Beacons app does not communicate properly, please contact the HPE Aruba TAC.
thanks herman, the missing control points caused our problems.
Chris, Please double-check that you have set the Control points on all of your maps. To ...
Please double-check that you have set the Control points on all of your maps. To do so, go to maps, press the 'Edit' (pencil) for each map, and set the control points:
I know it sounds strange to link delays to not setting the control points, but I have seen it happen a few times.
As a guidance always set the control points first thing when you start doing work on a map.