nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to connect to R710 after factory reset

unknown

Hi I factory reset a R710 AP and when I rebooted it I got the configure.meXXXXX SSID which requires a password.

I can connect to the configure.meXXXXX SSID wirelessly using the serial number of the AP as password but that's as far as I can get.

Both green PWR & CTL leds flash on AP.

I am unable to connect to it using 192.168.0.1. via web browser.

IP Scanner detects it at 192.168.0.1 & open ports 22 & 443 andI can ping it..

Any advice appreciated.
Thanks

Stephen

Find more posts tagged with

Accepted answers

All comments

sunny_gupta

Is it Unleashed?

Regardless, if you connect to Configure.Me SSID you should receive an address via DHCP on your client. Then would connect to the gateway IP available which is the AP.

Flashing PWR light means the AP did not receive an IP address from DHCP and so it defaults to 192.168.0.1. You can connect to this IP through the wired port. Connect your client to the switch and assign an IP like 192.168.0.10, then you can connect to the 192.168.0.1 address via CLI or Web UI.

unknown

thanks for prompt reply.

If I enter 192.168.0.1 into browser I don’t get web UI with Ethernet to 192.168.0.10.

Stephen

sunny_gupta

That's odd - can you successfully ping the 192.168.0.1?

If so, can you ssh in to the AP instead of HTTPs?

unknown

I reset to factory and rebooted but AP is the same.

I need to reinstall firmware ?

Stephen

unknown

Hi Sandeep,

I reset to factory using CLI command and rebooted.

But AP is the same...

From PuTTY:

Ruckus R710 Multimedia Hotzone Wireless AP
Version: 114.0.0.0.1294
OK
rkscli: GET IPADDR WAN
IP Address: (dynamic, vlan 1), IP: 192.168.0.1 Netmask 255.255.255.0 Gateway 0.0.0.0
OK
rkscli:

How do I install firmware ?

Stephen

unknown

Hi Sandeep,

I've run the CLI instruction fw show all

rkscli: fw show all
<Control Info>
ipaddr:
file: R710_114.0.0.0.1294.bl7
size: 15925248
MD5 : F1C066498CD733F77C94F961C43BD084
type: 0
local_file
-------------------------------------
current primary boot image is Image1
---------------<Image1 FW header>
Magic: RCKS
next_image: 0x280000
invalid: 0
hdr_len: 160
compression: l7
load_address: 0x42000000
entry_point: 0x42008000
timestamp: Wed Dec 18 00:59:41 2019
binl7_len: 15928248
hdr_version: 4
hdr_cksum: 0x84D6
version: 114.0.0.0.1294 ( 114.0.0.0.1294 )
MD5: F1C066498CD733F77C94F961C43BD084
product: r710 (0)
architecture: 0
chipset: 0
board_type: 0
board_class: 0
customer:
Image Sign Type: Intermediate Signed Image(ISI).
Tail start: 0xf2ff60
---------------<Image2 FW header>
Magic: RCKS
next_image: 0x280000
invalid: 0
hdr_len: 160
compression: l7
load_address: 0x42000000
entry_point: 0x42008000
timestamp: Wed May 2 11:28:02 2018
binl7_len: 12687196
hdr_version: 4
hdr_cksum: 0x057C
version: 110.0.0.0.663 ( 110.0.0.0.663 )
MD5: D906240EC4282ACEF948186EC184AF0C
product: r710 (0)
architecture: 0
chipset: 0
board_type: 0
board_class: 0
customer:
Image Sign Type: Intermediate Signed Image(ISI).
Tail start: 0xc18f60
OK

Stephen

sunny_gupta

Hi Stephen, seems you are able to login via CLI so that is good. If this is the case, can you not login to the AP via UI and browser to https://192.168.0.1 ? this will allow an easier upgrade of the code.

From the CLI you can follow these steps:

#fw set control R710_110.0.0.0.663.bl7 [where the filename is the one you want to upgrade to]

#fw set proto tftp

#fw set host 192.168.0.10 [where the IP is the TFTP server address]

#fw update

These steps should allow you to upgrade the firmware via CLI using a TFTP server. But i would try to login to the web management UI first and browse to the upgrade section - it will be easier.

eizens_putnins

Most probable reason of problems is corrupted firmware on AP. As far as you can connect to AP using SSH, from Ethernet port or through recovery SSID, you are good to upgrade firmware and probably can recover AP.

I had experience when whatever you do, you can't connect to AP using SSH or http, reset to factory didn't help, so AP was efficiently bricked and this required RMA. It doesn't happened with standalone image but with 5.1.xxx vSZ image after upgrade from previous version. This problem was 100% fixed in the latest release.

eizens_putnins

As AP has life-time warranty, open case with Ruckus, support will either help to resolve issue or arrange RMA.