Meru Networks AP1000 SERIES, Руководство по установке

Страница: 26 / 135

12 Meru Access Point Installation Guide
© 2010 Meru Networks, Inc.
Best Practices for an AP300/AP200 Network
Best Practices for an AP300/AP200 Network
Read this section if you have both AP200 and AP300 active simultaneously on the same network with ABG
legacy clients. The following best practices should be followed to get optimal performance from such a mixed
network.

Do not deploy AP200 and AP300 at the same physical location; we recommend no overlapping
coverage between AP200 and AP300.

If AP200 and AP300 must have overlapping coverage, make sure the ESS profiles on both AP types
are unique. The chart below shows two scenarios, one supported, one not supported.

AP300i and AP300 are interchangeable and fully compatible to share a virtual cell. It's like having
two AP300s with different antennas. The only difference is that AP300i is detected as a such in the
UI of the controller.
Assumptions for the above best practices include:

AP200 is using Virtual Port and BSSID Virtual Cell (AP200 could also be using Shared BSSID Virtual
Cell.)

AP300 is using Virtual Port BSSID Virtual Cell.

AP200s and AP300s are on the same channel. (AP200 and AP300 could also be on different channels.)

AP200s and AP300s are on the same controller. (AP200 and AP300 could also be on different
controllers as long as each controller has a unique controller index.)
Supported Scenario AP200 Configuration AP300 Configuration
Two Unique ESS profiles
ESS Profile name in
controller is UniqueName1 ESS Profile name in
controller is UniqueName2
AP200 and AP300 SSID string
over the air
Meru Meru
Unsupported Scenario AP200 Configuration AP300 Configuration
Same ESS profiles
ESS Profile name in
controller is same name ESS Profile name in
controller is same name
AP200 and AP300 SSID string
over the air
Meru Meru