Level 2 MiNT Links - Single AP importance

[Richard_Augusto]

Hello,

I have a question regarding Level 2 Links.

I noticed that when Level 2's adoption mode is activated, only one Access Point appears in each RF-Domain.

This single Access Point Access Point adopted, in the case by the VX9000, does something "different"? For example, if I have an adopted Access Point generating Crash Log, can it mess up the entire RF-domain, causing disconnects or something like that?

Thanks in advance.

[Daren_Ellis]

Its possible you do not have a control vlan correctly configured on your rf-domain.
If that is properly configured please ensure that all your APs at the site see each other as mint-neighbors on the control vlan you selected.

[ckelly]

I'm not entirely sure by what you mean when you say "only one Access Point appears in each RF-Domain" but when you have a Distributed deployment (controller in NOC and APs in remote sites) you should be using Level-2 MiNT links between each site (RF-Domain) and the controller.

At each RF-Domain, one of the APs will be automatically elected as the RF-Domain manager and will retain its level-2 MiNT link with the controller. All of the other non-RF-Domain manager APs at the site (RF-Domain) will drop their initial existing level-2 links with the controller and then just establish level-1 MiNT links with all the other APs within the RF-Domain (including whichever AP is the acting RF-Domain manager. From that point forward, stats and other communications between the controller and the site's APs are effectively 'proxied' through the RF-Domain manager AP. All of this is automatic.

The elected RF-Domain manager still behaves as an AP...but it also takes on some additional responsibilities. Examples would be collection of RF-stats from the other APs within the same RF-Domain, which it then uses to make decisions about channel/power planning and will tell the other APs what power/channel to use (if using SmartRF).
Another extra responsibility would be the distribution of firmware. When the controller tells a site (RF-Domain) to upgrade its firmware, the controller pushes out only 1 copy of the image to the RF-Domain manager AP at each site (RF-Domain). The RF-Domain manager will then distribute the image to the other APs within the RF-Domain...and then finally will upgrade itself.

In the event that the currently elected RF-Domain manager AP goes down (for whatever reason) another election will automatically take place, and another AP takes over.

As far as an adopted AP generating a crash log messing up the entire RF-Domain? Nope.