Can SSIDs on Merakis MR46 and old APs like AIR-CAP17021* have seamless transitions on 7925 phones ?

[PierreRosello]

Can SSIDs on MR46 and old wifi APs like AIR-CAP17021-E-K9 have seamless transitions ?

what are the requirements to make sure both are compatible ?

Currently we have SSIDs on the MR46s with the following configurations:

-Pre Shared Key

-splash page : none

-Client IP assignment : Layer 3 Roaming

-VLAN 140

-Dual Band operation

-Minimum Bitrate : Full compatibility with legacy devices (pre-1999)

what needs to be done on the wireless controller SSIDs to make it compatible with the cisco meraki SSIDs ?

[PierreRosello]

another question, how can we ensure that the meraki SSIDs are compatible with cisco phones model 7925 ?

We are experiencing frequent downtimes (meaning, the cisco phones are disconnecting at random intervals even when we are right next to the wifi AP, so the signal strength is at it's peak) with our current meraki MR46 setup.

For instance, we tried to fix it by changing the Layer 3 Roaming option to Bridged Mode in order to enable 802.11r, and the phones could not get their IP at all. (stuck on the IP configuration, Expiration DHCP, and Configuration CM list steps) So we reverted it back, and the phones can connect again, but again we get downtimes at random intervals.

With our current meraki setup, what would be the best way to fix this Meraki SSID -> Cisco 7925 compatibility issue ?

[KarstenI]

---

@PierreRosello wrote:

another question, how can we ensure that the meraki SSIDs are compatible with cisco phones model 7925?

---

Wow, the newest APs and the oldest wireless handset. This device is EOL for some time and only supports outdated wireless standards. I would try to replace these.

[KarstenI]

With PSKs, roaming is not that critical as it will not take very long. Still both are separate systems that will see each other as a rouge and will not cooperate. Best to not mix them in the same area.

---

-Minimum Bitrate : Full compatibility with legacy devices (pre-1999)

ok, everything is lost in your network ... 😉

[PierreRosello]

So you are saying that SSIDs on old Wifi APs like AIR-CAP172021-E-K9 and MR46 would not cooperate ? can you elaborate on why it would not do so ?

[KarstenI]

There are a couple of things. The three most important (IMO) are:

• For any kind of assisted roaming (which speeds up the roaming process), both APs need to be controlled by the same controller which is not the case here.
• For every RRM (radio resource management) where the controller tries to control which AP uses which channel and transmit power, only the "own" APs are controlled by one controller. All other APs evaluated but can't be controlled. It will not play nicely.
• For security, one controller typically wants to have full control of a given SSID. If an unknown system uses the same SSID, the controller by default sees that as an enemy as it could also be an attacker broadcasting this SSID to fool the clients. 

[rhbirkelund]

Just to make one thing clear... If you already have a Cisco WLC with 1702 APs joined to it, you can not simply go out an buy Meraki MR46's to have them join a Cisco WLC.

Meraki APs are incompatible with Cisco Classic (AireOS/IOS-XE WLC) infrastructure.

If your Meraki APs are broadcasting SSID A, and your 1702 APs are also broadcasting SSID A, your clients will essentially be roaming between two different infrastructures.
The clients will go through a complete Assoc/Auth process, each time the roam between a Meraki AP and a Cisco Classic AP.

[cmr]

@PierreRosello we do have some 7925s that have been working on our Meraki wireless infrastructure.  What we have is below:

Dedicated VLAN, subnet and SSID for phones

SSID is bridged mode

WPA2 PSK

802.11r and 802.11w both disabled

5GHz only

Bonjour forwarding disabled

12Mbps minimum bitrate

Make sure that wherever you are the phone can ideally see three APs for smooth roaming

Don't overload the 5GHz radios in the APs, for voice no more that 10 (yes, ten) client devices at a time is the recommended maximum for each AP, we have our busy SSIDs are 2.4GHz only to ensure this.