Specifications

AP Management From Controller
Altitude 35x0 Access Point Product Reference Guide288
MU associated, it sends the Radius packets on the wired side with its own IP Address as the source IPof
the request and the Destination IP Address of the Radius Server. In a local network implementation, the
APs, controller and Radius Servers are all on the same LAN and the routing works fine. However, when
the AP is adopted over a WAN link, the Radius Server IP Address will be an internal address which is
non-routable I over the Internet.
To access the Radius server’s non-routable IP address over the WAN, you have the option to configure
AP Radius Proxying for the WLAN. When this flag is enabled, the AP is reconfigured to send all radius
traffic to the controller and the controller does the proxying to the real Radius server to handle
authentication. The controller automates the process of handling Radius proxy configuration and client
configurations. The controller supports only one real radius server configuration without the presence
of realm information. To support multiple radius servers, a realm has to be associated with the real
Radius server.
When radius proxying is enabled without specifying a realm, the controller can no longer process
requests on the on-board radius server. You cannot authenticate using the on-board Radius server any
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 onboard Radius server can no longer be used to
authenticate users. If Proxy Radius is enabled for a WLAN with realm configured, then the onboard 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 with 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:
● An AP firmware upgrade will not be performed at the time of adoption from the wireless controller.
Instead, the firmware is upgraded using the AP-35xx’s firmware update procedure (manually or
using the DHCP Auto Update feature).