AP Management from Controller
longer because all authentications done by users without a realm are forwarded to the external radius
server, as configured for the WLAN with AP Radius Proxy.
NOTE
The Extreme Networks wireless LAN controllers support AP Radius proxy without specifying realm information. If AP
Proxy Radius is enabled without specifying realm information, the internal Radius server can no longer be used to
authenticate users. If Proxy Radius is enabled for a WLAN with realm configured, then the internal Radius server
can perform as usual.
NOTE
If AP Proxy Radius is configured, the onboard Radius server has to be enabled. By default the onboard Radius server
is disabled. To enable the onboard Radius server use the Web UI or issue the "service radius" command in the CLI.
Supported AP Topologies
The following AP topologies are supported:
Extended WLANs Only
●
Independent WLANs Only
●
Extended WLANs with Independent WLANs
●
Extended VLAN on Mesh Networking
●
Topology Deployment Considerations
When reviewing the AP topologies describes in the section, be cognizant of the following considerations
to optimize the effectiveness of the deployment:
There are two LAN interfaces on the AP35xx LAN port: LAN1 and LAN2. By default, LAN1 is the
●
primary LAN connection. LAN2 is only used for tunneled traffic.
An AP can use its LAN1 interface on the LAN port or WAN interface for adoption. The default
●
gateway interface is set to LAN1. If the WAN Interface is used, explicitly configure WAN as the
default gateway interface.
Extreme Networks recommends using the LAN1 interface for adoption in multi-cell deployments.
●
If you have multiple independent WLANs mapped to different VLANs, the AP's LAN1 interface
●
requires trunking be enabled with the correct management and native VLAN IDs configured.
Additionally, the AP needs to be connected to a 802.1q trunk port on the wired controller.
Be aware IPSec Mode supports NAT Traversal (NAT-T).
●
486
Summit WM3000 Series Controller System Reference Guide