Extreme Networks Altitude 4700 Series, Product Reference Manual

Page: 611 / 648

Altitude 4700 Series Access Point Product Reference Guide
611
●
Extended WLANs with Independent WLANs on page 612
●
Extended WLAN with Mesh Networking on page 612
Topology Deployment Considerations
When reviewing the AAP topologies describes in the section, be cognizant of the following
considerations to optimize the effectiveness of the deployment:
●
An AAP firmware upgrade will not be performed at the time of adoption from the wireless
controller. Instead, the firmware is upgraded using the firmware update procedure (manually or
using the DHCP Auto Update feature).
●
An AAP can use its LAN1 interface 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 AAP's LAN1 interface
requires trunking be enabled with the correct management and native VLAN IDs configured.
Additionally, the AAP needs to be connected to a 802.1q trunk port on the wired controller.
●
Be aware IPSec Mode supports NAT Traversal (NAT-T).
Extended WLANs Only
An extended WLAN configuration forces all MU traffic through the controller. No wireless traffic is
locally bridged by the AAP.
Each extended WLAN is mapped to the Access Point's virtual LAN2 subnet. By default, the Access
Point's LAN2 is not enabled and the default configuration is set to static with IP addresses defined as all
zeros. If the extended VLAN option is configured on the controller, the following configuration updates
are made automatically:
●
The AAP’s LAN2 subnet becomes enabled
●
All extended VLANs are mapped to LAN2.
NOTE
MUs on the same WLAN associated to the AAP can communicate locally at the AP Level without going
through the controller. If this scenario is undesirable, the Access Point's MU-to-MU disallow option should be
enabled. To enable the Access Point’s MU-to-MU disallow option, see
“Creating/Editing Individual WLANs” on
page 148 .
Independent WLANs Only
An independent WLAN configuration forces all MU traffic be bridged locally by the AAP. No wireless
traffic is tunneled back to the controller. Each extended WLAN is mapped to the Access Point's LAN1
interface. The only traffic between the controller and the AAP are control messages (for example,
heartbeats, statistics and configuration updates).