Meru Technical Note - Default setting for VPort in 5.3 [USE CASE - Unable to add ESS to new APs]

[nmichael]

Description

QUESTION: Default setting for VPort in 5.3
[USE CASE - Unable to add ESS to new APs]

Scope

KB ARTICLE TYPE: Design/Configuration/Troubleshooting/Field Notice

RELATED PRODUCTS: AP320, AP301, AP302, AP310, AP311, AP433, AP1010, AP1020, AP1014, AP332, AP110

RELATED SOFTWARE VERSIONS: 5.3

KEYWORDS: VPort, VCell,

Solution
- In 5.3, provision has been made to accomodate Broadcom* and Atheros** based APs

- If an Atheros based AP is present in the AP-list, when creating a new ESSID, VPort will be set to ON.
- If there are only Broadcom based APs in the AP-list in the AP-list, VPort will be set to OFF when you attempt to create a new ESSID.
- By default, VCell is the topology recommended 5.3 onwards. Of course, when one has Atheros based APs, this is not possible (as explained above).

- Customers will usually this new design introduced when they add Atheros based APs to an existing Broadcom based AP network infrastructure.
- The symptom reported will be that they are unable to add APs to an ESSID.

Atheros: AP320, AP301, AP302, AP310, AP311, AP433

Broadcom: AP1010, AP1020, AP1014, AP332, AP110