Contents

WLAN Integration

To configure on-premise wireless controllers for use with a Cloud Integration Point (CIP), open Manage and select Configuration > WIPS > WLAN Integration.

For more information on how to configure a Cloud Integration Point (CIP), see Wi-Fi Cloud Integration with Third-Party Controllers using CIP.

These WLAN controllers are supported:

Aruba Mobility Controller

Integration with the Aruba wireless controller enables Wi-Fi Cloud to periodically retrieve information, such as wireless device details and signal strengths, from the Aruba Mobility Controller with SNMP (Simple Network Management Protocol). Wi-Fi Cloud uses this information to automatically classify devices managed by Aruba Mobility Controllers for WIPS security and tracks the location of devices detected by Aruba APs.

To add an Aruba Mobility Controller in Wi-Fi Cloud:

  1. Open Manage.
  2. Select Configuration > WIPS > WLAN Integration > Aruba Networks.
  3. Select the Aruba Integration Enabled check box.

Screen shot of Aruba controller integration page in Manage

  1. Click Add Controller.
  2. Configure the required options in the Wireless Controller Section:
  • Controller (IP Address/Hostname) — IP address or host name of the Aruba Mobility Controller Wi-Fi Cloud communicates with.
  • Port Number — Port number of the Aruba Mobility Controller from which data is imported.
  • CIP — From the CIP drop-down list, select a CIP-enabled WatchGuard AP that you want to use to communicate with Wi-Fi Cloud.
  • SNMP Version — Select SNMPv2 or SNMPv3.
  • Community String — User-defined community string that Wi-Fi Cloud uses to communicate with the Aruba Mobility Controller. The default value is public.

You must configure SNMP on the controller for SNMP communications to work correctly. On the controller, make sure that the Read Community String is set to the default public or your custom string in the controller SNMP configuration.

  • Data Import Enabled — Enable import of data from the Aruba Mobility Controller.
  • Import Managed APs — Import managed APs from the Aruba Mobility Controller.
  • Import Managed Clients — Import clients associated with APs managed by the Aruba Mobility Controller.
  • Import Managed Client Associations — Import information about client associations for APs managed by the Aruba Mobility Controller.
  • Import Unmanaged APs — Import APs not managed by the Aruba Mobility Controller.
  • Import Unmanaged Clients — Import clients associated with APs not managed by the Aruba Mobility Controller.
  • Import Unmanaged Client Associations — Import information about client associations for APs not managed by the Aruba Mobility Controller.
  • Import Signal Strength Information — Import signal strength information of managed devices from the Aruba Mobility Controller. Location tracking results can vary depending on the Aruba AP models used in the network.

Screen shot of the Aruba configuration page in Manage

  1. Click Save.

The Current Status field displays the status of the controller integration service:

  • Running — The service is running. The last time the data was retrieved from the controller is displayed.
  • In Process — This status appears for a short time immediately after you add a new controller and the service is in the process of collecting data from the controller for the first time. When Wi-Fi Cloud is ready to display the data, the status changes to Running.
  • Stopped — The service has stopped. The last time the data was retrieved from the controller before the service stopped is displayed.

These errors can appear:

  • A configured and enabled controller has a host name that cannot be resolved.
  • A configured and enabled controller is not reachable.
  • System server has stopped.
  • Internal error — You must contact WatchGuard Technical Support.

Imported APs displays the number of APs imported into Wi-Fi Cloud from the controller as of the last synchronization.

You can configure the Synchronization Interval from 15-60 minutes. Wi-Fi Cloud retrieves data from the controller one time each synchronization cycle. The default is 30 minutes.

Cisco Wireless LAN Controller (WLC)

When you integrate Wi-Fi Cloud with a Cisco Wireless LAN Controller (WLC), you can retrieve information, such as wireless device details and signal strengths, from the WLC using SNMP (Simple Network Management Protocol). Wi-Fi Cloud uses this information to automatically classify devices managed by the WLC for WIPS security and tracks the location of devices detected by Cisco APs.

These Cisco Aironet APs and WLCs are supported:

  • 1000, 1100, 1130, 1140, 1200, 1250, 1300, 1602, 2602, 3500, 3602, 3702
  • 1230, 1240 AG
  • 1815i, 1832i
  • WLCs with AireOS versions 4.2x to 8.2x
  • Cisco IOS based devices with Wireless Controller Module

To add a Cisco WLC in Wi-Fi Cloud:

  1. Open Manage.
  2. Select Configuration > WIPS > WLAN Integration > Cisco WLC.
  3. Select the WLC Integration Enabled check box.

Screen shot of Cisco WLC integration page in Manage

  1. Click Add Controller.
  2. Configure the required options in the Wireless Controller Section:
  • Controller (IP Address/Hostname) — IP address or host name of the WLC the Wi-Fi Cloud communicates with.
  • Port Number — Port number of the WLC from which data is imported.
  • CIP — From the CIP drop-down list, select a CIP enabled WatchGuard AP that you want to use to communicate with Wi-Fi Cloud.
  • SNMP Version — Select SNMPv2 or SNMPv3.
  • Community String — User-defined community string that Wi-Fi Cloud uses to communicate with the WLC. The default value is public.

You must configure SNMP on the controller for SNMP communications to work correctly. On the controller, make sure that the Read Community String is set to the default public or your custom string in the controller SNMP configuration.

  • Data Import Enabled — Enable import of data from the WLC.
  • Import Managed APs — Import managed APs from the WLC.
  • Import Managed Clients — Import clients associated with APs managed by the WLC.
  • Import Signal Strength Information — Import signal strength information of managed devices from the WLC. Location tracking results can vary depending on the Cisco AP models used in the network.

Screen shot of the Cisco WLC configuration in Manage

  1. Click Save.

The Current Status field displays the status of the controller integration service:

  • Running — The service is running. The last time the data was retrieved from the controller is displayed.
  • In Process — This status appears for a short time immediately after you add a new controller and the service is in the process of collecting data from the controller for the first time. When Wi-Fi Cloud is ready to display the data, the status changes to Running.
  • Stopped — The service has stopped. The last time the data was retrieved from the controller before the service stopped is displayed.

These errors can appear:

  • A configured and enabled controller has a host name that cannot be resolved.
  • A configured and enabled controller is not reachable.
  • System server has stopped.
  • Internal error — You must contact WatchGuard Technical Support.

Imported APs displays the number of APs imported into Wi-Fi Cloud from the controller as of the last synchronization.

You can configure the Synchronization Interval from 15-60 minutes. Wi-Fi Cloud will retrieve data from the controller one time each synchronization cycle. The default is 30 minutes.

Advanced Configuration

Wi-Fi Cloud does not support some Lightweight Access Points (LAPs), such as the AP1030 and AP1130. To support these APs, you can request a configuration bundle from WatchGuard Technical Support and import the bundle into Manage. Only a superuser can import a WLC configuration file. All other users, including the administrator, have only viewing rights.

In the Advanced Configuration section, select Use Custom WLC Configuration and then click Upload Custom Configuration File. Select a file to upload.

Screen shot of advanced Cisco WLC integration settings in Manage

The custom WLC configuration file from this bundle is used for all future WLC synchronization. The bundle is imported as a .tgz file. An error message appears if the file is not imported or if the file is corrupted.

HP Multi-Service Mobility (MSM) Controller

When you integrate with an HP Multi-Service Mobility (MSM) Controller, Wi-Fi Cloud can retrieve information to automatically classify devices managed by the controller.

To add an HP MSM controller in Wi-Fi Cloud:

  1. Open Manage.
  2. Select Configuration > WIPS > WLAN Integration > HP MSM Controller.
  3. Select the HP MSM Integration Enabled check box.

Screen shot of the HP MSM integration page in Manage

  1. Click Add Controller.
  2. Configure the required options in the Wireless Controller Section:
  • Controller (IP Address/Hostname) — IP address or host name of the MSM controller Wi-Fi Cloud communicates with.
  • Port Number — Port number of the MSM controller from which data is imported.
  • CIP — From the CIP drop-down list, select a CIP enabled WatchGuard AP that you want to use to communicate with Wi-Fi Cloud.
  • Authentication — Type of authentication that the MSM Controller uses. Select Secure HTTP (SSL / TLS) if the controller uses HTTPS for authentication. Select HTTP Authentication if the controller uses HTTP.
  • Username — User name for HP MSM controller HTTP authentication. This field appears only if HTTP Authentication is selected.
  • Password — Password for HP MSM controller HTTP authentication. This field appears only if HTTP Authentication is selected.
  • Using Client Certificate — Use a client certificate. This field is valid only if Secure HTTP authentication is selected. If the MSM Controller is configured to use client authentication, make sure that the Wi-Fi Cloud client certificate is uploaded to the trusted CA certificate store on the HP MSM controller.
  • Data Import Enabled — Import data from the MSM controller.

Screen shot of the HP MSM configuration in Manage

  1. Click Save.

The Current Status field displays the status of the controller integration service:

  • Running — The service is running. The last time the data was retrieved from the controller is displayed.
  • In Process — This status appears for a short time immediately after you have added a new controller and the service is in the process of collecting data from the controller for the first time. When Wi-Fi Cloud is ready to display the data, the status changes to Running.
  • Stopped — The service has stopped. The last time the data was retrieved from the controller before the service stopped is displayed.

These errors can appear:

  • A configured and enabled controller has a host name that cannot be resolved.
  • A configured and enabled controller is not reachable.
  • System server has stopped.
  • Internal error — You must contact WatchGuard Technical Support.

You can configure the Synchronization Interval from 15-60 minutes. Wi-Fi Cloud will retrieve data from the controller one time each synchronization cycle. The default is 30 minutes.

Give Us Feedback  ●   Get Support  ●   All Product Documentation  ●   Technical Search