Wireless Access

We have a client who insists on using Meraki for his switching infrastructure. His Sophos APs were "too slow" and he wanted new APs. 

He came to us and purchased 4x AP345 as a drop and replace solution. We've done this hundreds of times without an issue.

He plugs in the APs in to his 2x MS225-48FP switches (because Aruba is too expensive) and Houston, we have a problem.

1 of the APs simply will not boot

3 of the APs come up and receive their Aruba Central config but won't pass traffic on the SSIDs (1 is native VLAN, 1 is assigned - even tried local assigned)

Of the 3 that come up, 2 of them randomly restart...

So we ship them to our techs office to troubleshoot expecting all sorts of heavy lifting. This time, they are plugged in to a Cisco 2960 with a mfr date of 2008. One by one, each of the APs come up without issue. They all complain about the PoE, but they come up perfectly.

So the question is has anybody ran across interoperability issues with Meraki switches and Aruba APs? I can't seem to find anything online or in the community. 

Thank you in advance.

I've never seen issues personally with Meraki, but to assist with resolving the issues. Can you confirm the following: 

1 of the APs simply will not boot <- Do you have a console output to determine why the AP will not boot?

3 of the APs come up and receive their Aruba Central config but won't pass traffic on the SSIDs (1 is native VLAN, 1 is assigned - even tried local assigned) <- Is the AP connected to a trunk port with all the necessary client VLANs tagged? Have you tried using a different native vlan?

Of the 3 that come up, 2 of them randomly restart... <- what do you see in the logs or a console output?

We had the APs shipped back to our shop.

The AP that would not boot, came right up on the bench.

The other 3 APs came right up on the bench as well.

All 4 were plugged in to a Cisco 2960 from 2008. (lol)

We allowed all 4 to burn in and after 24 hours, 3 of them were stable. However, the one that failed to boot initially at the client site, went offline. The health graph is attached.

We plugged in the console cable, cleared the OS, cleared the settings, and this is the loop it is stuck in now. (File attached) It will stay in apboot mode and allow us to basically do whatever we want, but after loading the OS, it will do this over and over until we unplug it.

Attachment(s)

BD-WLB F6 Log.txt   8 KB 1 version

I would open a TAC case and seek to get it replaced.