vsz 5.2 and tp-link WR-710N

  • 1
  • Question
  • Updated 4 months ago
  • Answered
Hi at all
i have upgraded my vsz from 10 days, and from this date, my 2 WR710N with static ip and configured in client mode they work only for a matter of seconds, then they are dead.
I can only restart them, and for few seconds they work well.
I'm not an expert in ruckus environment, then what log can i check ??
In Events & Alarm only 'WDS device joined' and nothing else :-(
Any idea ??

Photo of Corrado Ravinetto

Corrado Ravinetto

  • 6 Posts
  • 0 Reply Likes

Posted 5 months ago

  • 1
Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 500 Posts
  • 162 Reply Likes
Hi Corrado,

Could you try login into AP CLI (AP where these WR710N are trying to connect) and run below commands.

1- This one is to check on which SSID/wlanx your WDS device is connecting to.

get wlanlist

2- Identify the WLAN number from above command and then check if wds is enabled for it or not.

get wds-mode <wlan name>  ( eg - rkscli:get wds-mode wlan0 )

3- If above shows that wds mode is disable/off then run below command to enable WDS.

set wds-mode enable <wlan name> ( eg- rkscli:set wds-mode disable wlan0 )

Regards,
Syamantak Omer
Photo of Corrado Ravinetto

Corrado Ravinetto

  • 6 Posts
  • 0 Reply Likes
Hi mr Omer
i used your command on ap cli :
     rkscli: get wds-mode wlan32
     wlan32 WDS Mode: Enabled
and, as you can see, WDS Mode is enabled.....

any other idea ??

Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 500 Posts
  • 162 Reply Likes
Hi Corrado,

Try to factory reset WR710N and reconfigure them to connect with Ruckus WiFi.

You can also try using Troubleshoot options in vSZ GUI to see the communication between AP-client. This will help you to see at what point communication if failing.

You can also pull the AP support log just after connecting WR710N to network. In support log find the logs related to your client MAC.



Regards,
Syamantak Omer
Photo of Corrado Ravinetto

Corrado Ravinetto

  • 6 Posts
  • 0 Reply Likes
Hi Omer
i did what you suggest me:
- reset to factory default
- Troubleshoot 


The only one warning says : Timeout expired.
Nothing else.

Bye



Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 459 Posts
  • 148 Reply Likes
Hi Corrado,

If 4 way handshake is successful then just after frame-4, client should start sending DHCP/bootp "discover" frame to AP and I don't see it (because you seems configured static IP to client). In that case connection is successful and you will not see any other traffic in Troubleshoot.

Try setting your WDS device to DHCP and see if you can also get an IP (Run the troubleshooting again).

What about support information? Did you checked if there are some logs related to failing client MAC? Could you share the specific logs from support information for this client?

What is the WLAN configuration type, authentication type and encryption type?

Regards,
Syamantak
(Edited)
Photo of Corrado Ravinetto

Corrado Ravinetto

  • 6 Posts
  • 0 Reply Likes
Hi Omer
also the client have a static ip.
Today i'm not in office due covid, then i cannot try the setting you suggest me.

What kind of log  do i will check ??  On tplink device or ruckus ??
If it is ruckus, what's the log ??


Wlan is a normal Wpa2  in open method with all factory default

Bye
Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 459 Posts
  • 148 Reply Likes
Hi Corrado,

You have to download support log just after a test connection from Ruckus AP where client was connecting.



In support information, search for client MAC and see what logs you see.

Beyond this you may need to engage support and open a case. Radio (OTA) Packet captures and support information will be required to troubleshoot further.

Regards,
Syamantak Omer
Photo of Corrado Ravinetto

Corrado Ravinetto

  • 6 Posts
  • 0 Reply Likes
Hi Omer
this morning,i changed the authentication method from wpa2 to wep, more insecure, but with this system it is working.
VERY STRANGE: i have 2 WR-710N with same firmware release , same client connected beyond, same authentication and same encryptio, BUT only one it's working.

I'am confused.
Now i open a ticket on support center, because for only one the workaround fix the problem.
Bye
Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 415 Posts
  • 136 Reply Likes
Hi Corrado,

Beyond this you may not be able to troubleshoot hence engaging support is a good idea.

Support should be able to find by comparing working vs non-working packet captures collected from AP.

Regards,
Syamantak Omer
Photo of Corrado Ravinetto

Corrado Ravinetto

  • 6 Posts
  • 0 Reply Likes
many thanks