vsz 5.2 and tp-link WR-710N
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2020 03:28 AM
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 ??
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 ??
10 REPLIES 10
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2020 12:26 AM
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 ( 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 ( eg- rkscli:set wds-mode disable wlan0 )
Regards,
Syamantak Omer
Syamantak Omer
Sr.Staff TSE | CWNA | CCNA | RCWA | RASZA | RICXI
RUCKUS Networks, CommScope!
Follow me on LinkedIn
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
3- If above shows that wds mode is disable/off then run below command to enable WDS.
set wds-mode enable
Regards,
Syamantak Omer
Syamantak Omer
Sr.Staff TSE | CWNA | CCNA | RCWA | RASZA | RICXI
RUCKUS Networks, CommScope!
Follow me on LinkedIn
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2020 01:48 AM
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 ??
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 ??
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2020 04:22 AM
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
Syamantak Omer
Sr.Staff TSE | CWNA | CCNA | RCWA | RASZA | RICXI
RUCKUS Networks, CommScope!
Follow me on LinkedIn
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
Syamantak Omer
Sr.Staff TSE | CWNA | CCNA | RCWA | RASZA | RICXI
RUCKUS Networks, CommScope!
Follow me on LinkedIn
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2020 08:09 AM
Hi Omer
i did what you suggest me:
- reset to factory default
- Troubleshoot

The only one warning says : Timeout expired.
Nothing else.
Bye
i did what you suggest me:
- reset to factory default
- Troubleshoot
The only one warning says : Timeout expired.
Nothing else.
Bye

