White_Fi

You don't have some software offering out DHCP on your laptop do you? It is unheard of for 1 AP let alone 3 all doing the same?

Yes it should do unless the reset isn't performing correctly. Try again for 15 seconds in the pin hole. We may need to RMA this AP but I have never seen an AP that won't FR correctly. Odd one.

I see. Sorry i assumed that since the AP was not on default it was getting it from DHCP.. this is odd then. can you login to the AP with the ZD admin / password?

But the AP is still plugged into the network. So it will FR then DHCP request. It will also broadcast for a ZD. So either: 1) Keep AP on network... Go to ZD - config - access points - and disable AP auto join. Then FR AP and webgui into 10.42.0.1 and load standalone FW. When FW upgrade is complete either approve AP in ZD or enable AP Auto join 2)Get AP off network - Plug cable into laptop with IP 192.168.0.5/24 will do. FR the AP and browse to 192.168.0.1 and load standalone FW. When complete plug AP back into network. - - - Updated - - - 9.12.x is likely to be last release the 7363 will support.

The AP will be under ZD mgmt then. You can login with ZD admin credentials but you wont be able to load any firmware until it has been factory reset. If you want to keep it on the network and not isolate it for the FW upgrade please disable "Approve all APs automatically" under Configure - Access Points on your ZD then FR the AP. Or just FR it off the network without changing this ZD settings.

Sounds like it hasn't been factory reset... or if it has it has been reset and plugged into a network with DHCP. Can you web browse to the AP via that IP and load standalone AP software on it? You may need to factory reset and take off the network as it may be under mgmt from your ZD... which we want to avoid until we have a newer FW on it.

I can see the AP sending out for DHCP requests so it looks like it boots normally. If you can't ping it on 192.168.0.1 after a factory reset (pin in the hole for 10 seconds whilst powered) I would suggest requesting an RMA / RTF from Ruckus. Ensure that your adaptor is in this subnet and you are using a standard cat5 cable. Thanks

If the new VLANs are working in most parts of the school then it's safe to rule out your Ruckus configuration (unless you are using AP groups with overriding VLAN tags) and your core switch. I would focus on looking at the edge switches in the locations of failure. Does the client fail to obtain an IP address if you use Ethernet and untag the VLAN on a port at the edge? Double check that the VLANs are untagged (trunked) on the uplink ports. Thanks

Best setup would be to have the ZD and APs in there own VLAN or an existing mgmt VLAN. The switch ports should be untagged (native) on this VLAN and tag on any VLANs you wish to carry over the WLANs. It is not necessary to have the ZD switch ports also tagged with your WLAN VLANs unless you want to make use of the Bonjour Gateway feature on the ZD.

The ZD3000 is fine but I would consider upgrading the AP as the 7363 are EOL and 9.12.x is going to be the last supported revision for the APs. High-end smartphones and tablets do have 802.11ac chipsets and some are even MU-MIMO ready, such as the Galaxy S6. Samsung are likely to capitalise with releasing a new phone rather than enable the feature on the current handset but it shows "wave-2" ac features are out there and ready. With that in mind the question is do you go "wave1" with the R5/6/700 or straight in with the R710 "wave2" to support, in my eyes, the only big 802.11ac features that makes sense in an enterprise wireless network: MU-MIMO. And that feature is a game changer for wireless capacity in general.

There are bug fixes in 9.12.1 that fix watchdog timeouts for the 7363 APs. It is still recommended to free some memory up ont he AP by disabling IPv6 (if not in use) and disable NTP

Yes the 7363 is supported on 9.12.1.0.140. However, I believe 9.12 may be the last support release for the 7363 AP. Thanks

Great thank you. First i would recommended upgrading the ZD3000 to the latest 9.12.1 FW as it does contain not only AP bug fixes but captive portal fixes. When newer devices are released (Android 5.x for example). Google changed the way the device handles the captive portal. The newer Ruckus ZD code also contain changes to its Captive Portal engine in order to support newer OS'. You will need to upgrade to a flavor of 9.9 before continuing to the upgrade to 9.12. As always, save the config backup file the ZD will offer you when you upload the fw .img file. Regards

Hello, Could you let me know what ZD version and firmware is running on the ZD and what AP models you have? Many thanks

Hi gmbaxter, iBoss is focused around scale-ability and the standard appliance that we supply for secondaries is good for up to 10,000 users. Further more, being a gigabit capable layer2 network bridge it doesn’t have the bottleneck issues of proxy based devices, so you will only need the one SWG box. Let us know if you’d like us to setup a web or onsite demo for you.