UAM is also one of the authentication methods supported by the EWS controller, besides other authentication methods such as 802.1X authentication and auto login by the controller based on the MAC addresses and/or IP addresses of the devices used. Furthermore, the EWS controller also supports customization to the behavior of UAM through a UAM filter and provides UAMD log. Please click here to know more.
Normally, when a user moves from an edge AP managed by one Controller to another edge AP managed by another Controller, the user would experience network disconnection and have to re-login. However, with Cross Gateway Roaming, the user can stay logged in to the network and continue to enjoy network access without interruption.
Cross Gateway Roaming adopts a star topology that consists of one Master Node that sits at the center and multiple Slave Nodes that connect to it. One Master Node may connect with up to 15 Slave Nodes. A Controller can be in Master Mode or Slave Mode depending on its Cross Gateway Roaming settings.
This technical guide aims to explain the setup flow of Cross Gateway Roaming on the Controller. Below are two exemplary network deployments that deploy Cross Gateway Roaming so that authenticated users could seamlessly roam within the larger network. Please Click here to know more.
In this technical guide, the authentication flow on the controller is illustrated using a flowchart. With this flowchart, readers would be able to understand the order in which authentication methods are presented on the controller, so they could better plan the authentication methods they'd like to leverage as well as better understand how they could troubleshoot if necessary.
Furthermore, as will be seen from the flowchart, a variety of authentication methods are available on the controller for network access control, including web-based, 802.1X, WISPr and MAC authentication. How each authentication method works and where to configure its settings are also explained.
Please click here to know more details.
- The Site-to-Site VPN feature on the controller is introduced, and guidance on how to build and configure an exemplary site-to-site VPN is provided through step-by-step explanations. Click here to know more details.
- The Remote VPN feature on the controller is introduced, and guidance on how to setup and configure remote VPNs on the controller as well as on client devices is provided. Click here to know more details.
There are multiple types of logs and reports in the Controller, as described in the following:
a. CAPWAP Log
b. Configuration Change Log
c. Local Monthly Usage
d. Local Web Log
e. Micros Opera Log
f. On-Demand Billing Report
g. RADIUS Server Log
h. SIP Call Usage Log
i. SMS API Log
j. System Log
k. UAMD Log
l. User Events
In this guide, mechanisms of these different MAC address-based access control options are explained and a comparison between them is given. Possible scenarios for these MAC address-based access control options are also illustrated. Moreover, step-by-step configuration guides are provided to facilitate the configuration process. Click here to know more details.
This technical guide should help network administrators to easily setup and configure bandwidth limitation for all users in the network. Click here to know how to setup the User Bandwidth Throttling.
For PMS other than Micros Opera, a table of attributes is provided in this guide for system integrators to achieve integration with the Controller. Implementation examples are also given to help system integrators plan and carry out integration.
With such integration, the following can be achieved
1. Check-in information entered into the PMS by the hotel receptionist can be used as Wi-Fi login credentials
2. Data usage of each logged-in guest can be monitored and managed from the Controller
3. The Controller can send billing plan rate the user chose to the PMS as part of the check-out information
After reading this document, the reader should have a clear understanding of how user data from existing PMS can be used in authenticated Wi-Fi services and how to pragmatically set up the integration on the Controller. Click here to know more details for Third Party PMS Intergration.
1. Using the Wireless Controller as an external RADIUS server (Local and/or On-Demand databases) for a remote gateway
2. Using the Wireless Controller as a RADIUS server in 802.1X authentication (transparent login)
Note that for the first scenario, the remote gateway can be an Edgecore Wireless Controller or a third-party controller, and multiple remote gateways can be setup. Detailed configuration are shown in the following chapters.
This technical guide provides the administrator with instructions on how to setup the scenarios above for different applications. Verification from the client side is also shown in the end of the document. Click here to download the Technical Guide!
How to identify what kind of ''Failure Message''on Configuration Status of ECW7220-L/EWS4502 series and solve it, specific for country code?
1. After the AP managed by AC, but the configuration status still displayed 'Failure'.
System > WLAN > WLAN Configuration > Managed AP > Status > Summary
2. Users can check the reason of failure on the 'Detail!? page, the error is the setting about Country Code.
System > WLAN > WLAN Configuration > Managed AP > Status > Detail
3. Please changes to the correct country code.
System > WLAN > WLAN Configuration > Global > WLAN Switch
Check the country code of ECW7220-L.
Manage > Wireless Settings
*By default, if ECW7220-L has been managed by EWS4502 then web management interface will be disabling.
User may use following command to enable/disable the web interface via CLI.
ECW7220-L-7fa540# set web-server http-status up/down
System > WLAN > WLAN Configuration > Managed AP > Status > Summary
1. Set the Wired Network Discovery VLAN ID to 10. Wired Network Discovery VLAN ID is the management VLAN that AP will using to communicate with AC controller after success managed by AC controller.
(When the value not set to zero, means enabled VLAN classification at ALL AP that using this profile)
2. Modify the VLAN at corresponding VAP that want to enabled (default VLAN is 1)
3. Then apply the profile to take effect the configuration. (Remember need configure corresponding VLAN at the switch first before apply the profile.)
The EWS4502 with highest priority in the same cluster becomes the Cluster Controller.
If the priority is the same, the switch with lowest IP address will be the Cluster Controller.
And the highest cluster priority is 255.
AC cluster Scenario
How to configure the cluster priorty
Manage Page: System > WLAN > WLAN Configuration > Global
1. Configure the cluster priority of EWS4502-1 192.168.1.30 to 255.
*The highest cluster priority is 255, thus EWS4502-1 will become the Cluster Controller.
2. Configure the cluster priority of EWS4502-2 192.168.1.31 to 1.
How to check and ensure the cluster priority applied
Manage Page: System > WLAN > Status/Statistics > Peer Switch
Users can know which AC is the current cluster controller and which AC will manage AP.
1. Peer switch status of Cluster Controller EWS4502-1 192.168.1.30.