topic Re: 2nd Ruckus R710 AP Not Connecting to Existing Network in Access Points - Indoor and Outdoor

2nd Ruckus R710 AP Not Connecting to Existing Network

ryan_lee — Wed, 07 Jul 2021 22:49:48 GMT

Hello,

I am currently trying to setup a second Ruckus R710, however, it is not connecting with my master ap. With that, it is displaying a new configure.me ssid, this time asking for its serial number for the password, which I didn't have to do the first time. In addition to this, my computer is displaying that the configure.me has no internet connection, therefore, I cannot connect to its default ip address. I have tried doing a factory reset and have also tried applying a static ip to the configure.me. Nothing has worked so far.

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

syamantakomer — Thu, 08 Jul 2021 12:32:11 GMT

Hi Ryan,

Configure.me will appear if AP is in factory default mode and cannot discover the controller (master AP).

First check if your AP is getting IP address from the network or not (for this you need a DHCP server in wired network and switch should also be configured correctly).
If you don't have a DHCP server for AP management, connect a laptop directly to 2nd port of your AP (make sure AP is getting 802.3at power, in order to use 2nd eth port) and configure default subnet IP on laptop.
Access the AP over it's default IP, configure an IP address on same subnet as master AP.
Once configured, SSH into this AP and then ping master AP IP address. If you are able to ping it, means network connection is fine.
Check and make sure AP is on 200.x version, in order to discover and join master AP.

If above doesn't work, please feel free to open a support case and support team will help you.

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

ryan_lee — Thu, 08 Jul 2021 20:36:35 GMT

Thank you for your replay Omer,

I am fairly new to this so please excuse my confusion, but how would I check if I have a DHCP server? Is this through the switch? Also, if I do not have a DHCP server, what where and what I would enter for default subnet ip?

Thank you again,

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

ryan_lee — Thu, 08 Jul 2021 20:36:54 GMT

*reply

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

syamantakomer — Thu, 08 Jul 2021 22:15:31 GMT

Hi Ryan,

Could you confirm how your network devices are connected at present?

For example,

ISP connection >>> Modem/Router>>>> Switch >> APs

You have to first find out who is the DHCP server. It can be your ISP modem/router or switch.

Try to connect a devices on same subnet as your master AP and then run a IP scanner. It will give you more info like if your second AP got IP address from server or not, what is the gateway MAC address (refer the gateway IP of your laptop, when it is connected to wired network).

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

ryan_lee — Thu, 08 Jul 2021 22:45:12 GMT

Hello,

That is exactly how my network devices are connected: AT&T Fiber >>> Arris BGW210 >>> ICX-7250 >>> Five Ruckus R710's (Eventually once this is resolved). I have found out that my ISP router is the DHCP server. Also, the second AP is not displaying an ip on the same subnet as the master ap. Would this be a switch issue then?

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

syamantakomer — Fri, 09 Jul 2021 10:46:57 GMT

Hi Lee,

Check if switch ports are configured with identical config. You can review working vs non working switch ports on ICX.

show run int eth x/x/x (where x/x/x is the switch port number. For example 1/1/1)

Compare the SW port configuration of working vs non working SW ports where working and non working AP are connected.

Yon also swap the APs and see if non working AP comes online, it will rule out the SW configuration issue.

If you are able to access the non working AP over it's default IP, please run below commands and confirm details.

get version
get ipaddr wan
get director

Pull the output of same commands from a working AP as well.

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

ryan_lee — Fri, 09 Jul 2021 16:27:59 GMT

Hello,

Here are my results after the show run command (port 6 is the one that the working ap is connected to, port 1 is not):

SSH@ICX7250-24P Switch(config)#show run int eth 1/1/6
interface ethernet 1/1/6
speed-duplex 1000-full
!
SSH@ICX7250-24P Switch(config)#show run int eth 1/1/1
interface ethernet 1/1/1
speed-duplex 1000-full
!

After switching the non-functioning ap from port 1 to 6, nothing has changed. I also ran the commands for the functioning ap, as the non-functioning ap is yet to post an ip address to access via the web interface. Let me know if you want me to share the outputs with you.

Thank you,

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

syamantakomer — Fri, 09 Jul 2021 17:06:31 GMT

Hi Ryan,

Yes, share the other requested output from working AP CLI.

I think AP is not getting IP address, that is the problem. If you want to fix it quickly connect a laptop to the AP, assign static IP of same subnet as other APs and see if it fixes the issue.

Command to set static IP is:

set ipaddr wan xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy zzz.zzz.zzz.zzz

reboot

Where,

x= IP addresss

y= subnet

z= gateway

Bdw, switch is running on single broadcast domain it seems (no VLANs are configured).

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

ryan_lee — Fri, 09 Jul 2021 17:31:46 GMT

Hello,

ruckus(ap-mode)# get version
Ruckus R710 Multimedia Hotzone Wireless AP
Version: 200.10.10.5.229
OK
ruckus(ap-mode)# get ipaddr wan
IP Address: (static, vlan 1), IP: 192.168.1.126 Netmask 255.255.255.0 Gateway 192.168.1.254
OK
ruckus(ap-mode)# get director
------ Unleashed Info ------
Device role : controller-ap
Primary Controller : n/a
Secondary Controller : n/a
DHCP Opt43 Code : 3

The information of the most recent Unleashed:
[1] 192.168.1.126
[2] 192.168.1.131

AP is under management of Unleashed: 192.168.1.126 / ec:8c:a2:25:d4:10,
Currently AP is in state: RUN
OK

Would I assign an ip through the cli? Because I am unable to ssh into the nonfunctioning ap's default ip address even after factory resetting multiple times.

Also, for the switch, is it a bad thing that no vlans are configured. How does that contribute to the issue?

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

eizens_putnins — Sun, 11 Jul 2021 19:47:39 GMT

Check that your master AP isn't set in gateway mode.

But it actually looks that second AP was connected at some moment to master. Also it seems that both AP got IP from gateway -- .126 master and .131 the other one.

No VLANs is not good for security, but it is easier for troubleshooting.

For the very beginning I would recommend disconnect the 1st (working Unleashed AP), reset and connect second one and check if it will get IP address and become Unleashed master. If yes, nothing is that bad with it. If not try to upgrade/replace firmware image, it may be corrupted.

Post results....

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

ryan_lee — Sun, 11 Jul 2021 22:59:21 GMT

Thank you for the reply,

My master ap is not set in gateway mode. Also, the .126 and .131 ip addresses cam from the master, I just changed it from dynamic to static for easier access.

After disconnecting the master, resetting and reconnecting the second ap, it is still not getting an ip from the dhcp server. (I am still getting an APIPA ip during ip scan as well as "no internet, secured" message on my computer from configure.me ssid.) My CTL light is also still flashing green. Interestingly, I bought 5 APs new to add to unleashed network, however, they appear to all be doing the same thing, all showing no internet under ssid, which was not the case when setting up my first.

I have another question: how would I upgrade/replace firmware image on second ap if I'm not getting an ip to ssh or login via web cli? Unless, is there another way that I am missing?

Thank you again,

Re: 2nd Ruckus R710 AP Not Connecting to Existing Network

syamantakomer — Mon, 12 Jul 2021 14:08:06 GMT

Hi Ryan,

I would suggest you to open a case with support.

If all new APs are doing the same thing then there must be something wrong in the network side.

Changing firmware will not fix network issue. AP should get an IP address if wired network is configured correctly.

Before you reach out to support, try below tests as well.

1. Access the master AP and check if AP is getting 802.3at power (get power-mode).

2. If step 1 is true, power up a non-working AP, factory reset it by pushing and holding the reset button for 12 seconds. Once FD is done, connect this AP to 2nd port of your master AP.

3. Check if AP is getting IP address or not. Similarly, you can also connect a laptop to 2nd port of your master AP and see if laptop gets an IP. This will rule out network issue.

Note: Logically, config.me cannot provide internet connection. It is just for AP access and configuration purpose.