ZD 1100 not recognizing/provisioning AP 7363 or any AP

[bore_clement]

Hi,
i have just put a ZD1100 online, and trying to connect some 7363 with no luck : in any case, it says that the AP is accepted, but afterwards either it says "upgrade failed" or it does nothing at all, waiting for 10 to 100 minutes... we did try one of the 7363 on another working ZD1100, it worked flawlessly upgrade and configuration.

I tried upgrading firware, then downgrading, factory reset... still same issue; updates on the ZD went smooth though, no trouble switching from a version to another.

With the "stock" firmware or with the latest, nothing to do : AP's get an IP for a DHCP server on the lan, the are displayed on the ZD, but nothing else...

I saw a SSH command to add controler IP to an AP, but didn't worked out.

Any idea how to resolve this one?

I have to say i though Ruckus ZD's were fault free... :p

Regards

[keith_redfield]

Have you tried directly connecting the 7363 to the ZD? If not, can you describe how they are connected? (intervening devices and configuration). And are you using *any* vlans?

[bore_clement]

Thanks for trying to help

Yes i did try that, and even mutliple switches, cables, ac adapters... In fact, i found out the troublemaker was the DHCP server ; i don't really know why, it gave correct ip infos, but was messing with the AP's.

The DHCP was provided by a Wifi gateway (called UCOPIA) , providing advanced captive portal, logging and interface with specific software ; as soon as we managed to get this dhcp server/gateway updated, it worked flawlessly.

So, the ruckus hardware is neat! And support is really good too, quick and efficient.

Thanks a ton

Regards,

[keith_redfield]

Awesome! Thx for providing the resolution - I hate mysteries 🙂

[joakim_wasseng_]

Had the same problem as described in the heading (though not exactlly the same as PARIS INN)

After a power outage in one of my sites all my AP 7363 were stuck in provisioning after they regained power. I could log on to the AP:s directlly, but rebooting them did nothing, still stuck in provisioning. I resolved this issue by lowering the "Tunnel MTU"-value (Configure / Access Points) from default 1500 to 1400. All AP:s then got connected within 5 min. This having to do with package sizes getting to large and not fragmenting as they should.

Thought someone reading this post might find this info usefull 🙂