Floorplan Manager Integrations

HPE Aruba Networking Central supports floorplan manager integration with different applications, where administrators can import floorplans backup file from supported applications in HPE Aruba Networking Central. The supported applications include the following:

  • Classic Central

  • Airwave

  • Ekahau

  • Hamina

Supported File Formats

Classic Central and Airwave

While importing floorplans from Classic Central and Airwave application into HPE Aruba Networking Central, you can import only .zip file formats.

Ekahau

While importing floorplans from Ekahau application into HPE Aruba Networking Central, you can import both .zip file formats and.ESX file formats.

Note:

  • For Ekahau, the device match for an imported floor is based on the device name whereas, for HPE Aruba Networking Central and AirWave the device match is based on device name, device MAC address, and device serial number. If the device is not present or the device attributes do not match, the AP replacement is ignored.

  • For Ekahau, the wall type of the imported floor is matched with the wall type already present in HPE Aruba Networking Central based on the attenuation value. If wall types with same attenuation are not present, then it is created. For HPE Aruba Networking Central and AirWave, wall attenuation is not a part of the floorplan backup file. If you want to restore wall attenuation from these applications, you must create custom wall types in HPE Aruba Networking Central before importing any floor. If wall type with matching attenuation is not present, then the wall attenuation is set to "Drywall" for walls on the imported floor.

Hamina

While importing floorplans from Hamina application into HPE Aruba Networking Central, you can import only .zip (OpenIntent) file format.

Note:

For Hamina, there will be no floor number or ordinal associated to a floor name in the open intent file, so the system will assign the floor numbers automatically in ascending order. Users can edit the floor numbers as per requirement.

To initiate an integration, you must import the floorplan from the respective application. To import, complete the following steps:

  1. In the HPE Aruba Networking Central landing page, select a site from the Sites menu.

    Alternatively, you can click the expand icon on the Sites menu to search for a site from the list.

    The site dashboard is displayed with the network and connectivity information for the site.

    The HPE Aruba Networking Central page is set to the selected site context.

  1. From the Actions drop-down list, select Import Floors.

    The Import Floors page is displayed.

  2. Click Select File and browse in your system to upload the import floorplan file.

  3. Click Next.

    The import process takes time based on the size of the uploaded file. After the import is complete, you can see all the attributes of the imported floorplan. For more information on importing floorplans, see Importing Floors.

  4. Optionally, you can modify the properties of the floor that you are importing.

    1. Click the Building Name drop-down list and select Create Building.
      The Create Building page where you can change the building name and the type of the building from the respective drop-down list. You can perform all the steps like search sites, move buildings, move floors similar to a newly created building. For more information, see Creating Initial Floor and Building.

    2. Enter the new floor number, floor name, and the ceiling height.

    3. Click Finish.

This video displays the procedure to import a Hamina file into HPE Aruba Networking Central:

Additionally, you can also initiate Hamina floorplan integration through the API. For more information, see Hamina Integration.

Note:

  • When importing via this method, any device that is not present in the account is not converted into a planned AP.

  • If a device in the Hamina floor map shares the same name as a device in the HPE Aruba Networking Central floor map but has a different model number, AP auto match will not occur.

  • Walls and Zones are not included during imports performed through the API.