Supported adaptive ap topologies, Topology deployment considerations, Extended wlans only – Brocade Mobility 7131N-FGR Access Point Product Reference Guide (Supporting software release 4.0.0.0-35GRN and later) User Manual

Page 562

Advertising
background image

550

Brocade Mobility 7131N-FGR Product Reference Guide

53-1001947-01

Supported adaptive AP topologies

10

Supported adaptive AP topologies

For this version of the access point firmware, the following AAP topologies are supported:

Extended WLANs only

Independent WLANs only

Extended WLANs with independent WLANs

Extended WLAN with mesh networking

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
switch. 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.

Brocade 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 switch.

Be aware IPSec Mode supports NAT Traversal (NAT-T).

Extended WLANs only

An extended WLAN configuration forces all MU traffic through the switch. 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 switch, 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 switch. 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 121.

Advertising