Specifications

BPG_11n_v1.0 | Page 17
Multi-controller Deployments
Excluding when the Inter-Controller Roaming (ICR) feature is used, roaming between
controllers would results in a hard handoff (i.e., Authentication/Association/DHCP) and a new
IP address being issued to the client. Again, plan where hard handoffs will happen. Use
natural boundaries.
Another consideration is VLAN assignments in a multi-controller deployment. The
recommended best practice is to use different VLAN addresses on different controllers.
Inter Controller Roaming (ICR)
Inter-controller roaming preserves client IP address when roaming from one controller to
another. ICR enables clients to roam between controllers without interrupting client
application sessions.
The recommendation is to use ICR when IP retention is a requirement.
Migration from AP200 to AP300
When migrating from AP200 to AP300 it is generally recommended that the migration
happen in big chunks, so to speak. A migration process that proceeds floor by floor or wing
by wing will typically be less disruption to network availability.
There is a possibility of over deployment with the method of one-to-one replacement as the
AP300, with its ability to do MIMO, has the potential to provide greater coverage per AP than
AP200. If it is determined that there are too many APs, some APs may be decommissioned.
If external antennas were used on the AP200, only two leads were used to connect the
antennas to the AP. With the AP300 there are 6 antenna connectors. To reuse the antennas
that were previously used by the AP200 (with just 2 leads) the 4 extra/unused leads of the
AP300 will need to be terminated. This type of configuration is supported in build 3.6.1-MR4
or later.
2.4 GHz: use A6, terminate A4 and A5.
5 GHz: use A1, terminate A2 and A3.
Summary of Recommendations for network comprised of AP200s and AP300s
The following best practices should be followed to get optimal performance from a network
that includes both AP200s and AP300s.
Here are the assumptions for best practices below.
MERU BEST PRACTICES GUIDE | 11n Design, Implementation and Optimization