cancel
Showing results for 
Search instead for 
Did you mean: 

No roaming between AP7522 and AP510-1, both types of AP's are adopted into VX9000

No roaming between AP7522 and AP510-1, both types of AP's are adopted into VX9000

AdrianB
New Contributor II
Hi,

I had the 23 pieces of AP7522 model purchased in the past, and now I also bought 13th pieces of the AP510-1 model, for same warehouse. Both models are adopted by the same controller (VX9000) and now the problem we encounter is when we switch from a different AP to a different AP (as a model) and the roaming does not work and due to this our devices are disconnecting from our application, it only works between the same AP model. Please help us with a fix / advice.

I have a controller VX9000 on which i have adopted many AP's (510-1 and 7522). I have the same firmware on VX9000 as i have on the AP's - wing 7.7.1.1.
My problem consists in not having a roaming when i pass by from AP7522 zone to AP510-1 zone and viceversa. I have the same SSID with the same password and same vlan (1).

Kind regards,
Adrian
12 REPLIES 12

Angelo_Cargnel
New Contributor III
Hi Andrej,

there are still some problems in your configuration:


But first of all I need to understand your setup a bit more.
All your APs are in the same IP subnet, therefore I guess they are in the same VLAN too. Right? 
The WiNG design recommendations demand to have only one RF-domain in the same VLAN, but you have two. Is there any reason why you have two RF-domains?

If both RF-domains are a must, you can enable a feature called "controller assisted mobility". See article here: https://extremeportal.force.com/ExtrArticleDetail?an=000064277&_ga=2.238097472.1753213050.1656927942-634180282.1632906918

But I would recommend to have only one RF-domain if there is no good reason for two.



Furthermore, there are still some problems in your configuration:



"firewall-policy default" is still not configured. Especially the command " no stateful-packet-inspection-l2" is important for proper roaming

"profile ap410 AP410-DMA" has "mint level 1 area-id 888" configured. Please remove if one RF-domain is good enough (see above)
"profile ap360 AP360-DMA" has "mint level 1 area-id 888" configured. Please remove if one RF-domain is good enough (see above)
"profile ap7522 AP7522-DMI". Please remove "aggregation ampdu max-aggr-size tx 65535" and "ldpc" from radio 1 and radio 2.
"ap410 00-DC-B2-37-9D-C4". Please remove "controller host 10.48.1.5" and 
"controller host 10.48.1.5 level 2". This AP will still connect by MiNT level 1.
"ap510-1 00-DC-B2-41-EF-65". Please remove " no mint mlcp vlan", "no mint mlcp ip" and "no mint mlcp ipv6". This AP will not adopt at all. So it will not receive any configuration from the controller and it will not "talk" to any RF-domain manager.

"ap510-1 00-DC-B2-42-14-A9". Please remove "no mint mlcp vlan" and "mint mlcp ip". This AP will not talk to any RF-domain manger.
"ap7522 84-24-8D-DE-0F-BC" has not static IP address and therefore can't adopt.
"ap360 00-DC-B2-3C-67-32" has configured "controller host 10.48.1.5". Please remove as the AP is trying to adopt by MiNT level 1 but it fails due to the different MiNT level 1 area id:
2022-06-29 23:05:21:Ignoring MLCP Discover from 32.3C.67.32: mismatch in area ids theirs:888 ours:0

"ap410-37D94C" is offline. Please check.
show adoption offline
-----------------------------------------------------------------------------------------------------------------------------------------
MAC HOST-NAME TYPE RF-DOMAIN TIME OFFLINE CONNECTED-TO LAST-KNOWN-IP
-----------------------------------------------------------------------------------------------------------------------------------------
00-DC-B2-37-D9-4C ap410-37D94C ap410 DMA 8 days, 8:07:21 ap410-377536:ge1 10.56.11.100
------------------------------------------------------------------------------------------------------------------------------------------

There are some settings in your configuration which should be changed, but they are more "cosmetic" and will not harm roaming.



Best regards,
Angelo

Hi Angelo,

Last Friday evening, we did following three modifications and seems that the issue has been fixed.

1. We specify min value 12 for both 2.4 and 5GHz in Smart RF. We modify to use just the channels 36,40,44,48 on 5GHz as I we saw some dfs events.
"%RADIO-4-RADAR_DETECTED: Radar found on Radio 2 channel 100 width 40 freq 5500 MHz"

2. We update the firewall policy: https://extremeportal.force.com/ExtrArticleDetail?an=000078342

3. We removed low data rate from radios as "B" should not be there.


Suppose point 2 was the one who fixed our issue.

Thanks for your help.

Kind regards,
Andrei

arichter
Extreme Employee
Hallo Adrian, did you make sure, that both APs are on the same RF Domain ? BR Andreas

AdrianB
New Contributor II
Hello Arichter

Yes, they are on the same rf-domain, the same firmware version 7.7.1.1
They have the same subnet, same SSID with the same password, same vlan (1).
GTM-P2G8KFN