topic Re: ZF 7055 unable to connect after reboot in Access Points - Indoor and Outdoor

ZF 7055 unable to connect after reboot

faisal_cholayil — Thu, 06 Feb 2014 13:34:41 GMT

Hello,

I have new ZF 7055 and i configured as a standalone AP and working but if i reboot the AP i lost the connectivity and show assigning ip address and i unable to access the management ip too,The radio LED is blinking.
To access the AP i have to reset the device factory settings. i upgraded the image to 9.7 still the same, please advise.

Faisal

Re: ZF 7055 unable to connect after reboot

keith_redfield — Thu, 06 Feb 2014 18:14:58 GMT

What configuration changes are you making after you factory reset? Screen shots of the relevant screens will help. It's not a software issue.

Re: ZF 7055 unable to connect after reboot

faisal_cholayil — Sun, 09 Feb 2014 06:34:07 GMT

Hi Keith,

Thank you for the response and i realized the issue, i think it because i assigned Vlan1 for Wireless access because i saw that Vlan1 is already assigned for management, when i use Vlan2 with different network on local subnet the issue not there.

Faisal

Re: ZF 7055 unable to connect after reboot

faisal_cholayil — Sun, 09 Feb 2014 07:56:01 GMT

Hello Keith,

I thought i was able figured out the issue but not yet.
Below is the changes i did
step 1:

Step2:
It works but if i reboot the device, i will lose both access (management and wirelss)

Re: ZF 7055 unable to connect after reboot

keith_redfield — Mon, 10 Feb 2014 16:02:16 GMT

Unfortunately, it sounds like faulty hardware. Please open a support case for further diagnostics. https://support.ruckuswireless.com/co...

Re: ZF 7055 unable to connect after reboot

faisal_cholayil — Tue, 11 Feb 2014 07:06:30 GMT

Hi Keith,
My colleague found a solution. he change the country to UAE and set channel 6 and it works.

Thanks

Re: ZF 7055 unable to connect after reboot

keith_redfield — Tue, 11 Feb 2014 15:57:00 GMT

Excellent! - that's a new one for me.

Re: ZF 7055 unable to connect after reboot

peter_dohm — Wed, 12 Feb 2014 05:24:30 GMT

Keith, this is exactly the same issue I chimed in on early in January. I respectfully disagree with your assessment. I believe this is a software issue. At your prodding I returned my device after exactly this behavior. The replacement is doing exactly this, exactly as was reported in this forum post, just as the previous one did. Can we get to the bottom of this already? Stand alone access points are the only ones seeming to have this problem...

Btw, if I reboot it 10 times, maybe twice in ten will it bring up a wireless interface. If I factory reset, it works for "a while" before this behavior restarts.

Sorry 😞

Peter

Re: ZF 7055 unable to connect after reboot

keith_redfield — Wed, 12 Feb 2014 05:57:28 GMT

@Peter - if you read carefully above you'll see I disagree with my assessment too 🙂

Did you try the fix Faisal uncovered? Forums are a terrible place to troubleshoot and we give the best shot we can based on fairly limited/often confusing descriptions and available diagnostics. This is not an official support venue - if you have a business critical issue - please open a support case.

It's possible it's a software issue, but standalone ZF7055's are an extremely rare installation - it was designed for the hotel industry where controllers are virtually always used and typical installations are in the hundreds of APs.

A search of our case archives reveals exactly none matching these descriptions (I can't find one for you either). I also cannot locate the other post you refer to so if you can provide the URL that would help.

Meanwhile...anyone experiencing these exact symptoms that believes it's a software issue - please open a support case so that we can indeed get to the bottom of it. Reference this thread so that we can tie them together

Thx

Re: ZF 7055 unable to connect after reboot

keith_redfield — Wed, 12 Feb 2014 06:16:42 GMT

Also - the screenshots above show a local subnet defined but it's not actually used since his wireless is set for bridge-to-wan and both are trying to vlan tag the same ID. So it should be disabled (I missed this in initial glance).

We probably don't test for that config since it's a no-op even though the GUI allows it. It's possibly doing something odd with tagging. If the WLAN is bridging to the WAN interface, that's all you need and no local subnet need be (or should be) defined.