Newbie question about Aironet 1041 with Meraki MX64

[wilsonj1337]

Hi all,

I was asked by my branch president to take a look at our wireless network because the wireless connection in the building is flaky at best. I'm not the network admin, but I'm studying to go into networking and have a solid understanding of the basics.

I located our hardware and found that we are using a Meraki MX64 firewall and some Aironet 1041 APs. The two APs are connected to the Meraki through an unmanaged switch and a PoE injector.

The problem appears to be that end devices will not connect to either of the two APs I've located. There is a third "LDSAccess" AP somewhere in the building that I have yet to locate, and that's the only one I can connect to even if I'm only feet away from another AP. The LEDs on the two APs are solid green, which indicate that the device is working but has no clients, according to Cisco documentation. In doing research online, I've read that Aironet APs must be connected to a Wireless LAN Controller. Does the Meraki MX64 operate as a wireless LAN controller? I think that's my real question here. If not, that would explain (I think) why these APs are not working.

I'm new to the Meraki and Aironet devices, so there may be another issue here. Is there another reason that a device would not connect to the Aironet APs?

[russellhltn]

The first step is to ask the Stake Technology Specilist to look at Technology Manager (tm.lds.org) to check the status of your building. The APs need to find and connect to their controller which is managed by the church.

[Biggles]

I've read that Aironet APs must be connected to a Wireless LAN Controller. Does the Meraki MX64 operate as a wireless LAN controller? I think that's my real question here. If not, that would explain (I think) why these APs are not working.

I'm new to the Meraki and Aironet devices, so there may be another issue here. Is there another reason that a device would not connect to the Aironet APs?

Having carried out all the Meraki MX64 changeover installations, for our FMG manager, I can say that the 1041 & 7021 AP's work with the MX64. However on a couple of installations, if I failed to reboot the MX64 after it was configured/activated, then added an additional 7021 (That is a story for another time) to the system. They were active when I left the building, but later on went to went to "sleep" as it were. When checking in TM, the 7021 had been disabled. Enabling the "switch" brought them back to life!

Although my experience was with 7021 AP's the same would apply to the 1041's.

Is it possible that the MX64 hasn't been rebooted since installation?

[wilsonj1337]

Is it possible that the MX64 hasn't been rebooted since installation?

I don't know how long it's been there, but I'm sure that the power has gone out sometime in the last few months. Last time I looked at it I did cycle power to the Meraki as well as both APs, although I'm not sure in which order - or if it matters.

I'll be looking at it again after church this Sunday with the Branch Clerk and one of the stake technology specialists. Do stake technology specialists have login credentials for the Meraki firewalls, or is that managed by another entity?

[lajackson]

Do stake technology specialists have login credentials for the Meraki firewalls, or is that managed by another entity?

The Global Service Center manages the firewalls, but the STS is able to access a good bit of information concerning firewall status, is able to reboot the firewall remotely if needed, and can even force a configuration refresh now without contacting the GSC.

[Biggles]

If the STS has the standard calling, that gives him the necessary credentials to access TM, but he will already be aware of that. There are other standard callings that also give access to TM.

FWIW - My first action, after checking for disconnected cables, with internet/firewall problems is to power the whole system down. Nine times out of ten this usually sorts things out!